Go to homepageCyberStrike

Menu

Star on GitHub · 3.2k
Sign inDownload

CVE-2026-31474

7.8 · HIGH

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 acces…

Published Apr 22, 2026CWE-416EPSS 0.14%

Overview

CVE-2026-31474 is a high-severity vulnerability. It was published on April 22, 2026 and has a CVSS 3.1 base score of 7.8 (HIGH).

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical 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.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

References

Refgit.kernel.org/stable/c/2e62e7051eca75a7f2e3d52d62ec10d7d7aa358cRefgit.kernel.org/stable/c/424e95d62110cdbc8fd12b40918f37e408e35a92Refgit.kernel.org/stable/c/9649d051e54413049c009638ec1dc23962c884a4Refgit.kernel.org/stable/c/cb3d6efa78460e6d50bf68806d0db66265709f64Refgit.kernel.org/stable/c/eec8a1b18a79600bd4419079dc0026c1db72a830Refaccess.redhat.com/errata/RHSA-2026:27288Refaccess.redhat.com/errata/RHSA-2026:27731Refaccess.redhat.com/errata/RHSA-2026:27789Refaccess.redhat.com/security/cve/CVE-2026-31474Refbugzilla.redhat.com/show_bug.cgi?id=2460646

How CyberStrike helps

Frequently asked questions

What is CVE-2026-31474?

CVE-2026-31474 is a high-severity vulnerability. It was published on April 22, 2026 and has a CVSS 3.1 base score of 7.8 (HIGH).

How severe is CVE-2026-31474?

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2026-31474?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-31474?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-31474 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2026

View all
Browse by year2026202520242023202220212020201920182017201620152014201320122011201020092008200720062005200420032002200120001999