PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-74700 Linux CVE debrief

A race condition vulnerability in the Linux kernel's net/sched: cls_api allows for a use-after-free attack. When destroying locked classifiers, the rtnl_lock is not always acquired, which can cause a race condition. This vulnerability has been resolved. The affected component is the Linux kernel's net/sched: cls_api. The vulnerability class is a race condition. The likely operational impact is a denial of service or potential code execution. The source-confidence limits are based on the provided CVE record and source references.

Vendor
Linux
Product
Unknown
CVSS
HIGH 7.8
CISA KEV
Not listed in stored evidence
Original CVE published
2026-08-22
Original CVE updated
2026-10-16
Advisory published
2026-08-22
Advisory updated
2026-10-16

Who should care

Linux kernel maintainers and users, as well as security teams responsible for monitoring and patching Linux kernel vulnerabilities. They should review and apply the provided patches to prevent potential attacks. The affected operator is the Linux kernel community. The platform impact is on Linux kernel-based systems. The vulnerability-management impact is on teams responsible for monitoring and patching Linux kernel vulnerabilities. The security-team is  

Why it matters

This vulnerability has a high impact on Linux kernel security, as it can lead to a denial of service or potential code execution. Linux kernel maintainers and users should review and apply the provided patches to prevent potential attacks.

  • Potential denial of service due to use-after-free attack
  • Potential code execution due to lack of rtnl_lock acquisition

Technical summary

The Linux kernel's net/sched: cls_api is vulnerable to a race condition attack. When destroying locked classifiers, the rtnl_lock is not always acquired, which can cause a use-after-free attack. This vulnerability has been resolved with the provided patches. The affected product context is the Linux kernel. The defensive impact is a high priority for Linux kernel maintainers and users, as it can lead to a denial of service or potential code execution. The source-grounded technical framing is based on the official CVE Program record and source references.

Defensive priority

High priority for Linux kernel maintainers and users, as it can lead to a denial of service or potential code execution.

Recommended defensive actions

  • Review and apply the provided patches to the Linux kernel
  • Ensure that the Linux kernel is updated to a version that includes the fix
  • Monitor the Linux kernel for any potential issues related to this vulnerability
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The vulnerability was introduced in the Linux kernel and has been resolved. The affected versions are prior to the fixed commits. The evidence is based on the official CVE Program record and source references. Defenders should verify the affected scope, severity, and vendor guidance. The CVE record was published on 2026-08-22T15:33:00.933Z and has not been modified since then.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-74700 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-74700

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-74700 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-74700

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

  • net/sched: cls_api: Always acquire rtnl_lock when destroying locked classifiers

    Unverified legacy reference

    URL: https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/74xxx/CVE-2026-74700.json

    cve_program_cvelist_v5

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/34e77d8e3570f9df3952496ddb402833695662fd

    Supplemental source

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/b648c8a56531aeabd1c14f6b5cf1891e269b3756

    Supplemental source

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/d6222af7274f08e7a1848131dc30319993d8f377

    Supplemental source

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/a81f9c44d87fb59d99fce72e29e02cab3a49a1c3

    Supplemental source

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/a347304b2ca1a5377d5bd2d8a72e4b4f12afe648

    Supplemental source

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.