CVE-2026-31474

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
7.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: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

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

can: isotp: fix tx.buf use-after-free in isotp_sendmsg()

isotp_sendmsg() uses only cmpxchg() on so->tx.state to serialize access to so->tx.buf. isotp_release() waits for ISOTP_IDLE via wait_event_interruptible() and then calls kfree(so->tx.buf).

If a signal interrupts the wait_event_interruptible() inside close() while tx.state is ISOTP_SENDING, the loop exits early and release proceeds to force ISOTP_SHUTDOWN and continues to kfree(so->tx.buf) while sendmsg may still be reading so->tx.buf for the final CAN frame in isotp_fill_dataframe().

The so->tx.buf can be allocated once when the standard tx.buf length needs to be extended. Move the kfree() of this potentially extended tx.buf to sk_destruct time when either isotp_sendmsg() and isotp_release() are done.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/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
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
1%
KEV
Not listed

Published

April 22, 2026

Last Modified

August 5, 2026

Advisory Details (5)

Auto-updated Jun 3, 2026
No patch confirmed yet.
generic

can: isotp: fix tx.buf use-after-free in isotp_sendmsg() - kernel/git/stable/linux.git - Linux kernel stable tree

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

can: isotp: fix tx.buf use-after-free in isotp_sendmsg() - kernel/git/stable/linux.git - Linux kernel stable tree

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

can: isotp: fix tx.buf use-after-free in isotp_sendmsg() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9649d051e54413049c009638ec1dc23962c884a4
generic

can: isotp: fix tx.buf use-after-free in isotp_sendmsg() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/424e95d62110cdbc8fd12b40918f37e408e35a92
generic

can: isotp: fix tx.buf use-after-free in isotp_sendmsg() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2e62e7051eca75a7f2e3d52d62ec10d7d7aa358c

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatkernel-0:6.12.0-55.82.1.el10_02026-06-22redhat
redhatkernel-0:5.14.0-687.17.1.el9_82026-06-22redhat
redhatkernel-0:6.12.0-211.26.1.el10_22026-06-20redhat
linuxKernel @ 6.6.131osv

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

(2 across 2 ecosystems)
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 (121 versions)6.19.11-1

Weakness Classification(2)

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

Additional Vendor Advisories

(13)

Data Freshness Timeline

(refreshed 6× in last 7d / 58× 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 232 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-31474?
CVE-2026-31474 is a high vulnerability published on April 22, 2026. In the Linux kernel, the following vulnerability has been resolved: can: isotp: fix tx.buf use-after-free in isotp_sendmsg() isotp_sendmsg() uses only cmpxchg() on so->tx.state to serialize access to so->tx.buf. isotprelease() waits for ISOTPIDLE via waiteventinterruptible() and then calls…
When was CVE-2026-31474 disclosed?
CVE-2026-31474 was first published in the National Vulnerability Database on April 22, 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-31474 actively exploited?
CVE-2026-31474 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 98.9% of all scored CVEs.
What is the CVSS score of CVE-2026-31474?
CVE-2026-31474 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-31474?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31474, 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-31474

Explore →

Is Your Infrastructure Affected by CVE-2026-31474?

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