Skip to main content
VulnerabilityPublished Updated

CVE-2026-72035: Linux kernel · NULL Pointer Dereference

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · CVSS 8.2 High · fixed in f60d5c12e0551012cee5c272b0bcbcc78f7bb506 : patch Linux kernel soon.

Data as of 26 Oct 2026, 14:18 UTC

CVSS 3.1 base score
8.2High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 47% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers can reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-10-16.

Patch
Available – fixed in f60d5c12e0551012cee5c272b0bcbcc78f7bb506, e056e1dfcddca877dd46d704e8ec9860cfc9ec44, e2b7ee61989f2d39df6c2cc06f9db1aea69bdb09 +5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 15 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 5a781ccbd19e4664babcbe4b4ead7aa2b9283d22, < f60d5c12e0551012cee5c272b0bcbcc78f7bb506
Fixed in
  • f60d5c12e0551012cee5c272b0bcbcc78f7bb506
LinuxLinuxAffected
  • ≥ 5a781ccbd19e4664babcbe4b4ead7aa2b9283d22, < e056e1dfcddca877dd46d704e8ec9860cfc9ec44
Fixed in
  • e056e1dfcddca877dd46d704e8ec9860cfc9ec44
LinuxLinuxAffected
  • ≥ 5a781ccbd19e4664babcbe4b4ead7aa2b9283d22, < e2b7ee61989f2d39df6c2cc06f9db1aea69bdb09
Fixed in
  • e2b7ee61989f2d39df6c2cc06f9db1aea69bdb09
LinuxLinuxAffected
  • ≥ 5a781ccbd19e4664babcbe4b4ead7aa2b9283d22, < 51f8af240aed903e988755af33d7491030b50ae9
Fixed in
  • 51f8af240aed903e988755af33d7491030b50ae9
LinuxLinuxAffected
  • ≥ 5a781ccbd19e4664babcbe4b4ead7aa2b9283d22, < 18d580cb00c55805633bae45e90cf22ed6b8e424
Fixed in
  • 18d580cb00c55805633bae45e90cf22ed6b8e424
LinuxLinuxAffected
  • ≥ 5a781ccbd19e4664babcbe4b4ead7aa2b9283d22, < 17ab5f76f3899f67e5569722f334591f4b88b17b
Fixed in
  • 17ab5f76f3899f67e5569722f334591f4b88b17b

Description

In the Linux kernel, the following vulnerability has been resolved: net/sched: sch_taprio: Replace direct dequeue call with peek and qdisc_dequeue_peeked When taprio's software path peeks a non-work-conserving child qdisc, the child stashes the peeked skb in its gso_skb; taprio_dequeue_from_txq() then takes the packet with a direct child ->dequeue() call, which ignores that stash, orphans the peeked skb and desyncs the child's qlen/backlog. With a qfq child this re-enters the child on an emptied list and dereferences NULL, panicking the kernel from softirq on ordinary egress. Take the packet through qdisc_dequeue_peeked(), as sch_red and sch_sfb now do. The helper returns the child's stashed skb first and is a no-op when there is none, so a work-conserving child is unaffected and the gated path now consumes the skb whose length was charged to the budget.

References

Community reviews

Loading reviews…