CVE-2025-40278

net: sched: act_ife: initialize struct tc_ife to fix KMSAN kernel-infoleak

N/A
Published: December 6, 2025 at 09:51 PM UTC
Updated: October 15, 2026 at 07:10 PM UTC
2 products affected across 2 vendorsLinux KernelRUGGEDCOM RST2428P Firmware

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: net: sched: act_ife: initialize struct tc_ife to fix KMSAN kernel-infoleak Fix a KMSAN kernel-infoleak detected by the syzbot . [net?] KMSAN: kernel-infoleak in __skb_datagram_iter In tcf_ife_dump(), the variable 'opt' was partially initialized using a designatied initializer. While the padding bytes are reamined uninitialized. nla_put() copies the entire structure into a netlink message, these uninitialized bytes leaked to userspace. Initialize the structure with memset before assigning its fields to ensure all members and padding are cleared prior to beign copied. This change silences the KMSAN report and prevents potential information leaks from the kernel memory. This fix has been tested and validated by syzbot. This patch closes the bug reported at the following syzkaller link and ensures no infoleak.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.6ef6980b6becb1afd9d82a4f043749a10ae81bf14
Vendor states this is fixed in 2191662058443e0bcc28d11694293d8339af6dde (fixed)
Vendor states this is fixed in 37f0680887c5aeba9a433fe04b35169010568bb1 (fixed)
Vendor states this is fixed in 5e3644ef147bf7140259dfa4cace680c9b26fe8b (fixed)
Vendor states this is fixed in 918e063304f945fb93be9bb70cacea07d0b730ea (fixed)
Vendor states this is fixed in a676a296af65d33725bdf7396803180957dbd92e (fixed)
Vendor states this is fixed in c8f51dad94cbb88054e2aacc272b3ce1ed11fb1e (fixed)
Vendor states this is fixed in ce50039be49eea9b4cd8873ca6eccded1b4a130a (fixed)
Vendor states this is fixed in d1dbbbe839647486c9b893e5011fe84a052962df (fixed)
Vendor states this is fixed in 4.6 (unaffected)
Vendor states this is fixed in 5.10.247 (unaffected)
Vendor states this is fixed in 5.15.197 (unaffected)
Vendor states this is fixed in 5.4.302 (unaffected)
Vendor states this is fixed in 6.1.159 (unaffected)
Vendor states this is fixed in 6.12.59 (unaffected)
Vendor states this is fixed in 6.17.9 (unaffected)
Vendor states this is fixed in 6.18 (unaffected)
Vendor states this is fixed in 6.6.117 (unaffected)
v < V4.0
Affected range stops below V4.0, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusDEFERRED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card