CVE-2026-31474

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: NoneExposed: 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:

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)
EPSS
1.2%
KEV
Not listed

Published

April 22, 2026

Last Modified

July 15, 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

Vendor Advisories for CVE-2026-31474(5)

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 @ 6.6.131—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.

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 38× 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 144 total refreshes for this CVE.

  1. 2026-07-22 14:08 UTCEPSS rescore
  2. 2026-07-22 14:08 UTCEPSS rescore
  3. 2026-07-21 15:24 UTCEPSS rescore
  4. 2026-07-21 15:24 UTCEPSS rescore
  5. 2026-07-20 20:02 UTCOSV refresh
  6. 2026-07-20 17:08 UTCEPSS rescore
  7. 2026-07-20 17:08 UTCEPSS rescore
  8. 2026-07-19 14:31 UTCEPSS rescore
  9. 2026-07-19 14:31 UTCEPSS rescore
  10. 2026-07-16 17:03 UTCEPSS rescore
  11. 2026-07-16 17:03 UTCEPSS rescore
  12. 2026-07-15 16:57 UTCEPSS rescore
  13. 2026-07-15 16:57 UTCEPSS rescore
  14. 2026-07-15 02:00 UTCEPSS rescore
  15. 2026-07-15 02:00 UTCEPSS rescore
  16. 2026-07-13 22:30 UTCEPSS rescore
  17. 2026-07-12 05:46 UTCEPSS rescore
  18. 2026-07-09 19:10 UTCEPSS rescore
  19. 2026-07-08 15:15 UTCEPSS rescore
  20. 2026-07-07 13:46 UTCEPSS rescore
  21. 2026-07-06 02:23 UTCEPSS rescore
  22. 2026-07-06 02:23 UTCEPSS rescore
  23. 2026-07-05 02:30 UTCEPSS rescore
  24. 2026-07-04 06:31 UTCEPSS rescore
  25. 2026-07-01 15:06 UTCEPSS rescore
Show 75 more
  1. 2026-06-30 23:22 UTCEPSS rescore
  2. 2026-06-29 14:06 UTCEPSS rescore
  3. 2026-06-29 14:06 UTCEPSS rescore
  4. 2026-06-28 14:07 UTCEPSS rescore
  5. 2026-06-28 14:07 UTCEPSS rescore
  6. 2026-06-28 04:56 UTCEPSS rescore
  7. 2026-06-28 04:56 UTCEPSS rescore
  8. 2026-06-27 03:08 UTCEPSS rescore
  9. 2026-06-25 13:49 UTCEPSS rescore
  10. 2026-06-25 13:49 UTCEPSS rescore
  11. 2026-06-24 14:05 UTCEPSS rescore
  12. 2026-06-23 21:33 UTCEPSS rescore
  13. 2026-06-23 21:33 UTCEPSS rescore
  14. 2026-06-22 14:25 UTCEPSS rescore
  15. 2026-06-22 14:25 UTCEPSS rescore
  16. 2026-06-21 14:56 UTCEPSS rescore
  17. 2026-06-21 14:56 UTCEPSS rescore
  18. 2026-06-21 01:59 UTCEPSS rescore
  19. 2026-06-19 19:25 UTCEPSS rescore
  20. 2026-06-19 19:25 UTCEPSS rescore
  21. 2026-06-18 17:52 UTCEPSS rescore
  22. 2026-06-18 17:52 UTCEPSS rescore
  23. 2026-06-17 17:53 UTCEPSS rescore
  24. 2026-06-16 17:52 UTCEPSS rescore
  25. 2026-06-15 17:49 UTCEPSS rescore
  26. 2026-06-15 04:52 UTCVendor advisory
  27. 2026-06-15 04:52 UTCGHSA enrichment
  28. 2026-06-14 23:18 UTCEPSS rescore
  29. 2026-06-14 16:50 UTCVendor advisory
  30. 2026-06-14 16:50 UTCGHSA enrichment
  31. 2026-06-13 23:00 UTCEPSS rescore
  32. 2026-06-12 23:12 UTCEPSS rescore
  33. 2026-06-12 23:12 UTCEPSS rescore
  34. 2026-06-12 02:51 UTCVendor advisory
  35. 2026-06-12 02:51 UTCGHSA enrichment
  36. 2026-06-11 14:48 UTCVendor advisory
  37. 2026-06-11 14:48 UTCGHSA enrichment
  38. 2026-06-11 14:00 UTCEPSS rescore
  39. 2026-06-10 22:18 UTCEPSS rescore
  40. 2026-06-10 15:50 UTCVendor advisory
  41. 2026-06-10 15:50 UTCGHSA enrichment
  42. 2026-06-10 13:22 UTCEPSS rescore
  43. 2026-06-10 03:49 UTCVendor advisory
  44. 2026-06-10 03:49 UTCGHSA enrichment
  45. 2026-06-09 15:48 UTCVendor advisory
  46. 2026-06-09 15:48 UTCGHSA enrichment
  47. 2026-06-09 03:47 UTCVendor advisory
  48. 2026-06-09 03:47 UTCGHSA enrichment
  49. 2026-06-08 14:17 UTCEPSS rescore
  50. 2026-06-08 14:17 UTCEPSS rescore
  51. 2026-06-08 08:39 UTCVendor advisory
  52. 2026-06-08 08:39 UTCGHSA enrichment
  53. 2026-06-07 20:38 UTCVendor advisory
  54. 2026-06-07 20:38 UTCGHSA enrichment
  55. 2026-06-07 15:25 UTCEPSS rescore
  56. 2026-06-07 15:25 UTCEPSS rescore
  57. 2026-06-07 15:25 UTCEPSS rescore
  58. 2026-06-07 08:36 UTCVendor advisory
  59. 2026-06-07 08:36 UTCGHSA enrichment
  60. 2026-06-06 20:35 UTCVendor advisory
  61. 2026-06-06 20:35 UTCGHSA enrichment
  62. 2026-06-06 13:47 UTCEPSS rescore
  63. 2026-06-06 13:47 UTCEPSS rescore
  64. 2026-06-06 05:33 UTCVendor advisory
  65. 2026-06-06 05:33 UTCGHSA enrichment
  66. 2026-06-05 22:47 UTCEPSS rescore
  67. 2026-06-05 22:47 UTCEPSS rescore
  68. 2026-06-05 17:14 UTCVendor advisory
  69. 2026-06-05 17:14 UTCGHSA enrichment
  70. 2026-06-05 03:28 UTCVendor advisory
  71. 2026-06-05 03:28 UTCGHSA enrichment
  72. 2026-06-04 13:59 UTCVendor advisory
  73. 2026-06-04 13:59 UTCGHSA enrichment
  74. 2026-06-04 13:12 UTCEPSS rescore
  75. 2026-06-04 13:12 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 July 15, 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 1.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-31474?
CVE-2026-31474 has a CVSS v3 base score of 7.8 (NVD).
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

Explore the affected products and dependency analysis for 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.

Start Free Scan →Browse All CVEs