Skip to main content
VulnerabilityPublished Updated

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

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · CVSS 9.1 Critical · fixed in e252db8ca2a01f82d472091f35d549b313278636 : patch Linux kernel as a priority.

Data as of 26 Oct 2026, 13:47 UTC

CVSS 3.1 base score
9.1Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 39% 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 e252db8ca2a01f82d472091f35d549b313278636, d110d7cdb045715c0b45b0dfd974525bb38f653d, c09a7446aab5773f38d6abb25fce99b8e1dfbc97 +5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 May 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
  • ≥ bc074524e123ded281cde25ebc5661910f9679e3, < e252db8ca2a01f82d472091f35d549b313278636
Fixed in
  • e252db8ca2a01f82d472091f35d549b313278636
LinuxLinuxAffected
  • ≥ bc074524e123ded281cde25ebc5661910f9679e3, < d110d7cdb045715c0b45b0dfd974525bb38f653d
Fixed in
  • d110d7cdb045715c0b45b0dfd974525bb38f653d
LinuxLinuxAffected
  • ≥ bc074524e123ded281cde25ebc5661910f9679e3, < c09a7446aab5773f38d6abb25fce99b8e1dfbc97
Fixed in
  • c09a7446aab5773f38d6abb25fce99b8e1dfbc97
LinuxLinuxAffected
  • ≥ bc074524e123ded281cde25ebc5661910f9679e3, < a85b46db143fda5869e7d8df8f258ccef5fa1719
Fixed in
  • a85b46db143fda5869e7d8df8f258ccef5fa1719
LinuxLinuxAffected
  • ≥ bc074524e123ded281cde25ebc5661910f9679e3, < 32372781d664a9b03c40343e96c29d0a6139f97d
Fixed in
  • 32372781d664a9b03c40343e96c29d0a6139f97d
LinuxLinuxAffected
  • ≥ bc074524e123ded281cde25ebc5661910f9679e3, < 520e8b4bcf872a534a7bf61ccf880047642df296
Fixed in
  • 520e8b4bcf872a534a7bf61ccf880047642df296

Description

In the Linux kernel, the following vulnerability has been resolved: btrfs: tracepoints: get correct superblock from dentry in event btrfs_sync_file() If overlay is used on top of btrfs, dentry->d_sb translates to overlay's super block and fsid assignment will lead to a crash. Use file_inode(file)->i_sb to always get btrfs_sb.

References

Community reviews

Loading reviews…