DEBIAN-CVE-2026-99219: Debian/linux vulnerability

Q: What conditions are required to trigger the fault?

The issue can be triggered by reading available_filter_functions while a kernel module is being loaded or unloaded. In that state, kallsyms_lookup() can fail without initializing the module name and offset values used by print_rec().

Q: What is the likely impact if the issue is triggered?

The uninitialized module-name pointer can pass a non-null check and be dereferenced by seq_printf(), causing a general protection fault and kernel oops. The provided data describes a crash condition, not privilege escalation or data disclosure.

Q: Is there a workaround if an updated kernel cannot be deployed immediately?

Avoid reading available_filter_functions during module load or unload activity. This reduces exposure to the described trigger condition, though it may not be practical where that interface is routinely monitored.

Q: How can administrators recognize that this issue may have occurred?

Kernel logs may show a general protection fault with a call trace involving string, vsnprintf, seq_printf, print_rec, t_show, and seq_read_iter. The event is associated with access to available_filter_functions during module state changes.

Published Nov 2, 2026

Updated

In the Linux kernel, the following vulnerability has been resolved: ftrace: Initialize modname and offset in printrec() printrec() leaves 'modname' and 'offset' uninitialized and kallsymslookup() 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 seqprintf(). Oops: general protection fault RIP: 0010:string+0x48/0xe0 Call Trace: vsnprintf+0x1f5/0x650 seqprintf+0x8e/0xb0 printrec+0x6c/0xc0 tshow+0x4c/0x440 seqreaditer+0x119/0x480 This can be triggered by reading availablefilterfunctions while a module is being loaded or unloaded. Initialize both variables so a failed lookup skips the module name.

Affected Software

3 affected componentsFixes available

debian/linux*

debian/linux<6.12.115-1

6.12.115-1

debian/linux*

Event History

Nov 2, 2026

CVE Published

via OSV·04:17 PM

Data Sourced

via OSV·04:17 PM

DescriptionAffected Software

Frequently Asked Questions

What conditions are required to trigger the fault?

The issue can be triggered by reading available_filter_functions while a kernel module is being loaded or unloaded. In that state, kallsyms_lookup() can fail without initializing the module name and offset values used by print_rec().

What is the likely impact if the issue is triggered?

The uninitialized module-name pointer can pass a non-null check and be dereferenced by seq_printf(), causing a general protection fault and kernel oops. The provided data describes a crash condition, not privilege escalation or data disclosure.

Is there a workaround if an updated kernel cannot be deployed immediately?

Avoid reading available_filter_functions during module load or unload activity. This reduces exposure to the described trigger condition, though it may not be practical where that interface is routinely monitored.

How can administrators recognize that this issue may have occurred?

Kernel logs may show a general protection fault with a call trace involving string, vsnprintf, seq_printf, print_rec, t_show, and seq_read_iter. The event is associated with access to available_filter_functions during module state changes.

DEBIAN-CVE-2026-99219: Debian/linux vulnerability

Affected Software

Event History

Frequently Asked Questions

What conditions are required to trigger the fault?

What is the likely impact if the issue is triggered?

Is there a workaround if an updated kernel cannot be deployed immediately?

How can administrators recognize that this issue may have occurred?

Company

Resources

Contact

Frequently Asked Questions

What conditions are required to trigger the fault?

What is the likely impact if the issue is triggered?

Is there a workaround if an updated kernel cannot be deployed immediately?

How can administrators recognize that this issue may have occurred?