Skip to main content
VulnerabilityPublished

CVE-2026-99219: Linux kernel · ftrace: Initialize modname and offset in print_rec()

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-99219· High

Not known to be exploited · fixed in e2e6fb972bfec4a0551bc7c185bdb17f78f94997 : patch Linux kernel soon.

Data as of 2 Nov 2026, 19:30 UTC

Severity
High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in e2e6fb972bfec4a0551bc7c185bdb17f78f94997, d97dba9ff13987d1fc415408557a54adde980311, 8932e5a4df110a25578728526bb5a3dbc849d8a2 +3

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: 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 2 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ b39181f7c6907dc66ff937b74758671fa6ba430c, < e2e6fb972bfec4a0551bc7c185bdb17f78f94997
Fixed in
  • e2e6fb972bfec4a0551bc7c185bdb17f78f94997
LinuxLinuxAffected
  • ≥ b39181f7c6907dc66ff937b74758671fa6ba430c, < d97dba9ff13987d1fc415408557a54adde980311
Fixed in
  • d97dba9ff13987d1fc415408557a54adde980311
LinuxLinuxAffected
  • ≥ b39181f7c6907dc66ff937b74758671fa6ba430c, < 8932e5a4df110a25578728526bb5a3dbc849d8a2
Fixed in
  • 8932e5a4df110a25578728526bb5a3dbc849d8a2
LinuxLinuxAffected
  • ≥ b39181f7c6907dc66ff937b74758671fa6ba430c, < 7271c064dd60d4456c5b90da757acd9420d06697
Fixed in
  • 7271c064dd60d4456c5b90da757acd9420d06697
LinuxLinuxAffected
  • ≥ b39181f7c6907dc66ff937b74758671fa6ba430c, < 753d5cba113a52cb155428f4ea93a4b0148c4bf1
Fixed in
  • 753d5cba113a52cb155428f4ea93a4b0148c4bf1
LinuxLinuxAffected
  • ≥ b39181f7c6907dc66ff937b74758671fa6ba430c, < 0e5ff07be834abaf4280e1dca7f9591e339d0960
Fixed in
  • 0e5ff07be834abaf4280e1dca7f9591e339d0960

AI-suggested

A fix has been made to initialize 'modname' and 'offset' in print_rec() to prevent dereferencing uninitialized variables. Users should apply the official kernel patch that addresses this issue. Until patched, avoid reading available_filter_functions during module load/unload if possible.

Description

A vulnerability in the Linux kernel's ftrace subsystem occurs because the variables 'modname' and 'offset' are left uninitialized in the print_rec() function. When kallsyms_lookup() fails, such as during module load or unload, 'modname' may contain garbage data that passes a check and is dereferenced, causing a general protection fault (kernel crash). This can be triggered by reading available_filter_functions while a module is being loaded or unloaded. The issue is resolved by initializing these variables to ensure failed lookups skip the module name.

References

Community reviews

Loading reviews…