CVE-2026-99219 json
ftrace: Initialize modname and offset in print_rec()
published 2026-11-02 6 d ago modified 2026-11-03 5 d ago also EUVD-2026-115261
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 6%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Linux Linux 6.1.191, 6.6.161, 6.12.115, 6.18.60, 7.2.14, 7.3.1, 7.4-rc1
- linux Debian 13 6.12.115-1
- linux Debian 14 7.2.14-1
debian advisories DEBIAN-CVE-2026-99219
- kernel Azure Linux 3.0 6.6.161.1-1
azure linux advisories AZL-112535
Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT
- git.kernel.org/stable/c/753d5cba113a52cb155428f4ea93a4b0148c4bf1 commit
- git.kernel.org/stable/c/0e5ff07be834abaf4280e1dca7f9591e339d0960 commit
- git.kernel.org/stable/c/e2e6fb972bfec4a0551bc7c185bdb17f78f94997 commit
- git.kernel.org/stable/c/8932e5a4df110a25578728526bb5a3dbc849d8a2 commit
- git.kernel.org/stable/c/7271c064dd60d4456c5b90da757acd9420d06697 commit
- git.kernel.org/stable/c/d97dba9ff13987d1fc415408557a54adde980311 commit
- git.kernel.org/stable/c/e1f339ff3b83857b93baf8b88186275a413d445e commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-99219 updated cvss 4.7
kernel: kernel: Denial of Service via uninitialized pointer dereference in ftrace
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 moreaffected: no fix planned “Out of support scope”
-
Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernel Red Hat OpenShift Container Platform 4 openshift/ose-rhel-coreos-9 Red Hat OpenShift Container Platform 5 openshift/ose-rhel-coreos-9, openshift/ose-rhel-coreos-10affected: no fix available “Fix deferred”
-
Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat OpenShift Container Platform 4 openshift/ose-rhel-coreos-8not affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.17% chance of exploitation in the next 30 days, higher than 6% of all scored CVEs (FIRST EPSS, 2026-11-08).
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/753d5cba113a52cb155428f4ea93a4b0148c4bf1
- git.kernel.org /stable/c/0e5ff07be834abaf4280e1dca7f9591e339d0960
- git.kernel.org /stable/c/e2e6fb972bfec4a0551bc7c185bdb17f78f94997
- git.kernel.org /stable/c/8932e5a4df110a25578728526bb5a3dbc849d8a2
- git.kernel.org /stable/c/7271c064dd60d4456c5b90da757acd9420d06697
- git.kernel.org /stable/c/d97dba9ff13987d1fc415408557a54adde980311
- git.kernel.org /stable/c/e1f339ff3b83857b93baf8b88186275a413d445e
Sources
- CVE List CVE-2026-99219
- NVD CVE-2026-99219
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.