CVE-2026-31474
Last modified
CVE-2026-31474 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. 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. EPSS estimates a 0.10% chance of exploitation in the next 30 days.
Description
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.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 6.4.1, < 6.6.131 | — |
| Linux | Linux Kernel | >= 6.7, < 6.12.80 | — |
| Linux | Linux Kernel | >= 6.13, < 6.18.21 | — |
| Linux | Linux Kernel | >= 6.19, < 6.19.11 | — |
| Linux | Linux Kernel | 6.4 | — |
| Linux | Linux Kernel | 7.0 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2026-31474?
How severe is CVE-2026-31474?
How do I fix CVE-2026-31474?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-31469In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-3147A vulnerability was found in libvips up to 8.18.0. This affe…7.8
- CVE-2026-31470In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-31471In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-31472In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-31473In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-31475In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-31476In the Linux kernel, the following vulnerability has been re…8.2
- CVE-2026-31477In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-31478In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-31479In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-3148A vulnerability was determined in SourceCodester Simple and …9.8
Are you affected by CVE-2026-31474?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
