Skip to main content
VulnerabilityPublished Updated

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

Affects Linux kernelSource CVE Database V5

0

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

Data as of 26 Oct 2026, 17:30 UTC

CVSS 3.1 base score
7.5High
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 f4de0777e4554a7de19c920accde6319dd530782, edc806f9122961f0d3819f7c69c14cccde31f277, c996a90f3071cf43683e5423da31aadbe002b8b4 +5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Jun 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
  • ≥ 11eeef41d5f63c7d2f7fdfcc733eb7fb137cc384, < f4de0777e4554a7de19c920accde6319dd530782
Fixed in
  • f4de0777e4554a7de19c920accde6319dd530782
LinuxLinuxAffected
  • ≥ 11eeef41d5f63c7d2f7fdfcc733eb7fb137cc384, < edc806f9122961f0d3819f7c69c14cccde31f277
Fixed in
  • edc806f9122961f0d3819f7c69c14cccde31f277
LinuxLinuxAffected
  • ≥ 11eeef41d5f63c7d2f7fdfcc733eb7fb137cc384, < c996a90f3071cf43683e5423da31aadbe002b8b4
Fixed in
  • c996a90f3071cf43683e5423da31aadbe002b8b4
LinuxLinuxAffected
  • ≥ 11eeef41d5f63c7d2f7fdfcc733eb7fb137cc384, < 711987ba281fd806322a7cd244e98e2a81903114
Fixed in
  • 711987ba281fd806322a7cd244e98e2a81903114
LinuxLinuxAffected
  • ≥ 11eeef41d5f63c7d2f7fdfcc733eb7fb137cc384, < 95be653a76793856ff8b2d8bd82c2943c23f5ca8
Fixed in
  • 95be653a76793856ff8b2d8bd82c2943c23f5ca8
LinuxLinuxAffected
  • ≥ 11eeef41d5f63c7d2f7fdfcc733eb7fb137cc384, < 83fc5dd63455a779ea2dd0f7ffee3c920919d80b
Fixed in
  • 83fc5dd63455a779ea2dd0f7ffee3c920919d80b

Description

In the Linux kernel, the following vulnerability has been resolved: netfilter: nfnetlink_osf: fix potential NULL dereference in ttl check The nf_osf_ttl() function accessed skb->dev to perform a local interface address lookup without verifying that the device pointer was valid. Additionally, the implementation utilized an in_dev_for_each_ifa_rcu loop to match the packet source address against local interface addresses. It assumed that packets from the same subnet should not see a decrement on the initial TTL. A packet might appear it is from the same subnet but it actually isn't especially in modern environments with containers and virtual switching. Remove the device dereference and interface loop. Replace the logic with a switch statement that evaluates the TTL according to the ttl_check.

References

Community reviews

Loading reviews…