CVE-2026-43035
Awaiting Analysis Awaiting Analysis - Queue
Heap Memory Leak in Linux Kernel Networking Subsystem

Publication date: 2026-05-01

Last updated on: 2026-05-01

Assigner: kernel.org

Description
In the Linux kernel, the following vulnerability has been resolved: net: sched: cls_api: fix tc_chain_fill_node to initialize tcm_info to zero to prevent an info-leak When building netlink messages, tc_chain_fill_node() never initializes the tcm_info field of struct tcmsg. Since the allocation is not zeroed, kernel heap memory is leaked to userspace through this 4-byte field. The fix simply zeroes tcm_info alongside the other fields that are already initialized.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-05-01
Last Modified
2026-05-01
Generated
2026-05-07
AI Q&A
2026-05-02
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
linux linux_kernel *
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN
Attack-Flow Graph
AI Powered Q&A
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

This vulnerability causes a kernel heap memory leak to userspace through an uninitialized 4-byte field in netlink messages. Such an information leak could potentially expose sensitive data residing in kernel memory.

Information leaks can impact compliance with data protection regulations like GDPR and HIPAA, which require protection of personal and sensitive data from unauthorized disclosure.

However, the provided information does not specify the exact nature of the leaked data or whether it includes personal or protected health information.

Therefore, while this vulnerability could pose a risk to compliance by enabling unauthorized data exposure, the exact impact on compliance with standards like GDPR or HIPAA cannot be determined from the given information.


Can you explain this vulnerability to me?

This vulnerability exists in the Linux kernel's networking code, specifically in the function tc_chain_fill_node which builds netlink messages. The function fails to initialize the tcm_info field of the tcmsg structure to zero. Because the memory allocated for this field is not cleared, it can leak leftover kernel heap memory to userspace through this 4-byte field.

The issue is fixed by zeroing the tcm_info field along with other fields during initialization, preventing the unintended information leak.


How can this vulnerability impact me? :

This vulnerability can lead to an information leak where sensitive kernel memory contents might be exposed to userspace applications. Such leaks can potentially reveal sensitive data or kernel memory layout information, which attackers could use to further compromise the system.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart