CVE-2026-31629

HIGHPre-NVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-04-24. the CNA's CVSS baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In the Linux kernel, the following vulnerability has been resolved:

nfc: llcp: add missing return after LLCP_CLOSED checks

In nfc_llcp_recv_hdlc() and nfc_llcp_recv_disc(), when the socket state is LLCP_CLOSED, the code correctly calls release_sock() and nfc_llcp_sock_put() but fails to return. Execution falls through to the remainder of the function, which calls release_sock() and nfc_llcp_sock_put() again. This results in a double release_sock() and a refcount underflow via double nfc_llcp_sock_put(), leading to a use-after-free.

Add the missing return statements after the LLCP_CLOSED branches in both functions to prevent the fall-through.

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
44(Track)
EG Risk 44/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity88% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
13%
KEV
Not listed

Published

April 24, 2026

Last Modified

August 5, 2026

Advisory Details (6)

Auto-updated May 2, 2026
No patch confirmed yet.
generic

nfc: llcp: add missing return after LLCP_CLOSED checks - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ff3d9e8f7244293e303f7b6ef70774291c7c27e9
generic

nfc: llcp: add missing return after LLCP_CLOSED checks - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/aba4712e8f0381cd5d196534ce2ad082626a5ab6
generic

nfc: llcp: add missing return after LLCP_CLOSED checks - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8977fad2b3c6eefd414131168d597c5d1d5e1abf
generic

nfc: llcp: add missing return after LLCP_CLOSED checks - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/796e0cac058252d0ad34ebe288e6f7979b5fc9b2
generic

nfc: llcp: add missing return after LLCP_CLOSED checks - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2b5dd4632966c39da6ba74dbc8689b309065e82c
generic

nfc: llcp: add missing return after LLCP_CLOSED checks - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0eb1263a3b8c36418c9ba295c9ab3abed664edbf

Vendor Advisories for CVE-2026-31629(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 5.10.258—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (54 versions)5.10.259-1—
linux-6.16.1.106-3~deb11u1 ... 6.1.174-1~deb11u1 (20 versions)6.1.176-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (129 versions)6.19.14-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(24)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 6× in last 7d / 30× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 266 total refreshes for this CVE.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 19:27 UTCEPSS rescore
  3. 2026-09-17 19:30 UTCEPSS rescore
  4. 2026-09-16 14:08 UTCEPSS rescore
  5. 2026-09-16 05:15 UTCEPSS rescore
  6. 2026-09-13 16:47 UTCEPSS rescore
  7. 2026-09-12 15:01 UTCEPSS rescore
  8. 2026-09-11 14:52 UTCEPSS rescore
  9. 2026-09-10 09:34 UTCEPSS rescore
  10. 2026-09-08 22:00 UTCEPSS rescore
  11. 2026-09-07 16:01 UTCEPSS rescore
  12. 2026-09-06 13:47 UTCEPSS rescore
  13. 2026-09-06 13:47 UTCEPSS rescore
  14. 2026-09-04 05:06 UTCEPSS rescore
  15. 2026-09-04 03:16 UTCOSV refresh
  16. 2026-09-02 14:11 UTCEPSS rescore
  17. 2026-09-01 13:53 UTCEPSS rescore
  18. 2026-09-01 04:39 UTCEPSS rescore
  19. 2026-09-01 04:39 UTCEPSS rescore
  20. 2026-08-30 19:17 UTCEPSS rescore
  21. 2026-08-30 01:22 UTCEPSS rescore
  22. 2026-08-28 21:41 UTCEPSS rescore
  23. 2026-08-27 14:25 UTCEPSS rescore
  24. 2026-08-26 14:46 UTCEPSS rescore
  25. 2026-08-25 13:49 UTCEPSS rescore
Show 75 more
  1. 2026-08-24 14:17 UTCEPSS rescore
  2. 2026-08-23 00:19 UTCEPSS rescore
  3. 2026-08-21 23:49 UTCEPSS rescore
  4. 2026-08-20 22:55 UTCEPSS rescore
  5. 2026-08-20 22:55 UTCEPSS rescore
  6. 2026-08-19 17:03 UTCEPSS rescore
  7. 2026-08-18 13:48 UTCEPSS rescore
  8. 2026-08-17 14:51 UTCEG score recompute
  9. 2026-08-17 14:51 UTCVendor advisory
  10. 2026-08-17 14:50 UTCGHSA enrichment
  11. 2026-08-17 13:47 UTCEPSS rescore
  12. 2026-08-16 14:56 UTCEPSS rescore
  13. 2026-08-16 05:47 UTCEG score recompute
  14. 2026-08-16 05:47 UTCVendor advisory
  15. 2026-08-16 05:47 UTCGHSA enrichment
  16. 2026-08-16 02:14 UTCEPSS rescore
  17. 2026-08-15 01:30 UTCEPSS rescore
  18. 2026-08-14 17:02 UTCVendor advisory
  19. 2026-08-14 17:02 UTCGHSA enrichment
  20. 2026-08-14 04:07 UTCEG score recompute
  21. 2026-08-14 04:07 UTCVendor advisory
  22. 2026-08-14 04:07 UTCGHSA enrichment
  23. 2026-08-13 22:00 UTCEPSS rescore
  24. 2026-08-13 08:31 UTCVendor advisory
  25. 2026-08-13 08:31 UTCGHSA enrichment
  26. 2026-08-12 17:49 UTCEG score recompute
  27. 2026-08-12 17:49 UTCVendor advisory
  28. 2026-08-12 17:49 UTCGHSA enrichment
  29. 2026-08-12 13:50 UTCEPSS rescore
  30. 2026-08-11 16:41 UTCEG score recompute
  31. 2026-08-11 16:41 UTCVendor advisory
  32. 2026-08-11 16:41 UTCGHSA enrichment
  33. 2026-08-11 02:09 UTCEG score recompute
  34. 2026-08-11 02:09 UTCVendor advisory
  35. 2026-08-11 02:09 UTCGHSA enrichment
  36. 2026-08-11 00:00 UTCEPSS rescore
  37. 2026-08-10 03:59 UTCVendor advisory
  38. 2026-08-10 03:59 UTCGHSA enrichment
  39. 2026-08-09 15:39 UTCEG score recompute
  40. 2026-08-09 15:39 UTCVendor advisory
  41. 2026-08-09 15:39 UTCGHSA enrichment
  42. 2026-08-09 13:46 UTCEPSS rescore
  43. 2026-08-09 03:19 UTCEG score recompute
  44. 2026-08-09 03:19 UTCVendor advisory
  45. 2026-08-09 03:19 UTCGHSA enrichment
  46. 2026-08-08 16:37 UTCEPSS rescore
  47. 2026-08-08 00:54 UTCEG score recompute
  48. 2026-08-08 00:54 UTCVendor advisory
  49. 2026-08-08 00:54 UTCGHSA enrichment
  50. 2026-08-07 12:34 UTCEG score recompute
  51. 2026-08-07 12:34 UTCVendor advisory
  52. 2026-08-07 12:34 UTCGHSA enrichment
  53. 2026-08-06 13:46 UTCEPSS rescore
  54. 2026-08-06 13:20 UTCVendor advisory
  55. 2026-08-06 13:20 UTCGHSA enrichment
  56. 2026-08-06 00:57 UTCEG score recompute
  57. 2026-08-06 00:57 UTCVendor advisory
  58. 2026-08-06 00:57 UTCGHSA enrichment
  59. 2026-08-05 19:17 UTCEPSS rescore
  60. 2026-08-05 12:38 UTCEG score recompute
  61. 2026-08-05 12:38 UTCVendor advisory
  62. 2026-08-05 12:38 UTCGHSA enrichment
  63. 2026-08-04 15:10 UTCEPSS rescore
  64. 2026-08-03 21:01 UTCEG score recompute
  65. 2026-08-03 21:01 UTCVendor advisory
  66. 2026-08-03 21:01 UTCGHSA enrichment
  67. 2026-08-03 10:36 UTCEPSS rescore
  68. 2026-08-02 23:41 UTCVendor advisory
  69. 2026-08-02 23:41 UTCGHSA enrichment
  70. 2026-08-02 11:21 UTCEG score recompute
  71. 2026-08-02 11:21 UTCVendor advisory
  72. 2026-08-02 11:21 UTCGHSA enrichment
  73. 2026-08-02 02:27 UTCEPSS rescore
  74. 2026-08-01 04:16 UTCEPSS rescore
  75. 2026-07-30 16:28 UTCEPSS rescore

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-31629?
CVE-2026-31629 is a high vulnerability published on April 24, 2026. In the Linux kernel, the following vulnerability has been resolved: nfc: llcp: add missing return after LLCP_CLOSED checks In nfcllcprecvhdlc() and nfcllcprecvdisc(), when the socket state is LLCPCLOSED, the code correctly calls releasesock() and nfcllcpsock_put() but fails to return. Execution…
When was CVE-2026-31629 disclosed?
CVE-2026-31629 was first published in the National Vulnerability Database on April 24, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-31629 actively exploited?
CVE-2026-31629 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 86.7% of all scored CVEs.
What is the CVSS score of CVE-2026-31629?
CVE-2026-31629 has a CVSS v4.0 base score of 8.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-31629?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31629, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-31629

Explore →

Is Your Infrastructure Affected by CVE-2026-31629?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs