CVE-2026-99219
ftrace: Initialize modname and offset in print_rec()
What happened?
In the Linux kernel, the following vulnerability has been resolved:
ftrace: Initialize modname and offset in print_rec()
print_rec() leaves 'modname' and 'offset' uninitialized and kallsyms_lookup() only sets them on success. When the lookup fails like when a module is being loaded or unloaded, 'modname' holds a garbage value, passes the 'if (modname)' check, and is dereferenced by seq_printf().
Oops: general protection fault RIP: 0010:string+0x48/0xe0 Call Trace: vsnprintf+0x1f5/0x650 seq_printf+0x8e/0xb0 print_rec+0x6c/0xc0 t_show+0x4c/0x440 seq_read_iter+0x119/0x480
This can be triggered by reading available_filter_functions while a module is being loaded or unloaded.
Initialize both variables so a failed lookup skips the module name.
Affected software and versions
| Software | Version information | Fixed version |
|---|---|---|
| LinuxLinux | affected: b39181f7c6907dc66ff937b74758671fa6ba430c to < 753d5cba113a52cb155428f4ea93a4b0148c4bf1; affected: b39181f7c6907dc66ff937b74758671fa6ba430c to < 0e5ff07be834abaf4280e1dca7f9591e339d0960; affected: b39181f7c6907dc66ff937b74758671fa6ba430c to < e2e6fb972bfec4a0551bc7c185bdb17f78f94997; affected: b39181f7c6907dc66ff937b74758671fa6ba430c to < 8932e5a4df110a25578728526bb5a3dbc849d8a2; affected: b39181f7c6907dc66ff937b74758671fa6ba430c to < 7271c064dd60d4456c5b90da757acd9420d06697; affected: b39181f7c6907dc66ff937b74758671fa6ba430c to < d97dba9ff13987d1fc415408557a54adde980311; affected: b39181f7c6907dc66ff937b74758671fa6ba430c to < e1f339ff3b83857b93baf8b88186275a413d445e | See vendor advisory |
| LinuxLinux | affected: 5.19; unaffected: 0 to < 5.19; unaffected: 6.1.191 to ≤ 6.1.*; unaffected: 6.6.161 to ≤ 6.6.*; unaffected: 6.12.115 to ≤ 6.12.*; unaffected: 6.18.60 to ≤ 6.18.*; unaffected: 7.2.14 to ≤ 7.2.*; unaffected: 7.3.1 to ≤ 7.3.*; unaffected: 7.4-rc1 to ≤ * | See vendor advisory |
Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.
Is it being exploited?
This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.
How to respond
- Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
- Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
- Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.
Sources and remediation references
- https://www.cve.org/CVERecord?id=CVE-2026-99219
- https://git.kernel.org/stable/c/753d5cba113a52cb155428f4ea93a4b0148c4bf1
- https://git.kernel.org/stable/c/0e5ff07be834abaf4280e1dca7f9591e339d0960
- https://git.kernel.org/stable/c/e2e6fb972bfec4a0551bc7c185bdb17f78f94997
- https://git.kernel.org/stable/c/8932e5a4df110a25578728526bb5a3dbc849d8a2
- https://git.kernel.org/stable/c/7271c064dd60d4456c5b90da757acd9420d06697
- https://git.kernel.org/stable/c/d97dba9ff13987d1fc415408557a54adde980311
- https://git.kernel.org/stable/c/e1f339ff3b83857b93baf8b88186275a413d445e