CVE-2026-99219: Linux kernel · ftrace: Initialize modname and offset in print_rec()
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in e2e6fb972bfec4a0551bc7c185bdb17f78f94997 : patch Linux kernel soon.
Data as of 2 Nov 2026, 16:32 UTC
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
Disclosed: evidence found.
CVE published 2 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
AI-suggested
A fix is available and has been applied in the Linux kernel commits identified by hashes e2e6fb972bfec4a0551bc7c185bdb17f78f94997, d97dba9ff13987d1fc415408557a54adde980311, 8932e5a4df110a25578728526bb5a3dbc849d8a2, 7271c064dd60d4456c5b90da757acd9420d06697, 753d5cba113a52cb155428f4ea93a4b0148c4bf1, and 0e5ff07be834abaf4280e1dca7f9591e339d0960. Users should update their Linux kernel to a version including these fixes to remediate the vulnerability.
Description
A vulnerability in the Linux kernel's ftrace subsystem was fixed by initializing the variables 'modname' and 'offset' in the print_rec() function. Previously, if kallsyms_lookup() failed during module load or unload, 'modname' could hold garbage data, leading to a general protection fault when dereferenced. This fault could be triggered by reading available_filter_functions while a module is loading or unloading.
References
- git.kernel.org/stable/c/753d5cba113a52cb155428f4ea93a4b0148c4bf1 (opens in a new tab)
- git.kernel.org/stable/c/0e5ff07be834abaf4280e1dca7f9591e339d0960 (opens in a new tab)
- git.kernel.org/stable/c/e2e6fb972bfec4a0551bc7c185bdb17f78f94997 (opens in a new tab)
- git.kernel.org/stable/c/8932e5a4df110a25578728526bb5a3dbc849d8a2 (opens in a new tab)
- git.kernel.org/stable/c/7271c064dd60d4456c5b90da757acd9420d06697 (opens in a new tab)
- git.kernel.org/stable/c/d97dba9ff13987d1fc415408557a54adde980311 (opens in a new tab)