Skip to main content
VulnerabilityPublished Updated

CVE-2026-43035: Linux kernel · net: sched: cls_api: fix tc_chain_fill_node to initialize tcm_info to zero to prevent

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in e35f5195cd44ff4053fbc5d71ea97681728a0099 : update Linux kernel when convenient.

Data as of 6 Nov 2026, 16:21 UTC

Severity
Low

Rated Low by Threat Radar's AI analysis · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-06.

Patch
Available – fixed in e35f5195cd44ff4053fbc5d71ea97681728a0099, e6e3eb5ee89ac4c163d46429391c889a1bb5e404, d6db08484c6cb3d4ad696246f9d288eceba2a078 +5

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 1 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 32a4f5ecd7381f30ae3bb36dea77a150ba68af2e, < e35f5195cd44ff4053fbc5d71ea97681728a0099
Fixed in
  • e35f5195cd44ff4053fbc5d71ea97681728a0099
LinuxLinuxAffected
  • ≥ 32a4f5ecd7381f30ae3bb36dea77a150ba68af2e, < e6e3eb5ee89ac4c163d46429391c889a1bb5e404
Fixed in
  • e6e3eb5ee89ac4c163d46429391c889a1bb5e404
LinuxLinuxAffected
  • ≥ 32a4f5ecd7381f30ae3bb36dea77a150ba68af2e, < d6db08484c6cb3d4ad696246f9d288eceba2a078
Fixed in
  • d6db08484c6cb3d4ad696246f9d288eceba2a078
LinuxLinuxAffected
  • ≥ 32a4f5ecd7381f30ae3bb36dea77a150ba68af2e, < 906997ea3766c24fbbf9cc4bf17c047315bbd138
Fixed in
  • 906997ea3766c24fbbf9cc4bf17c047315bbd138
LinuxLinuxAffected
  • ≥ 32a4f5ecd7381f30ae3bb36dea77a150ba68af2e, < 1091b3c174441a52fdbb92e2fe00338f9371a91c
Fixed in
  • 1091b3c174441a52fdbb92e2fe00338f9371a91c
LinuxLinuxAffected
  • ≥ 32a4f5ecd7381f30ae3bb36dea77a150ba68af2e, < 903c3405cfcc7700260e456ab66a5867586c9e69
Fixed in
  • 903c3405cfcc7700260e456ab66a5867586c9e69

AI-suggested

A fix is available and has been applied in the Linux kernel. The vulnerability is resolved by zero-initializing the tcm_info field in the affected function. Users should update to a Linux kernel version that includes the fix identified by the provided commit hashes. No additional mitigation steps are necessary once the kernel is updated.

Description

A vulnerability in the Linux kernel's network scheduler API (cls_api) was fixed by ensuring the tcm_info field in struct tcmsg is zero-initialized. Previously, this field was left uninitialized, causing kernel heap memory to be leaked to userspace via netlink messages. The fix involves zeroing tcm_info alongside other initialized fields to prevent this information leak.

References

Community reviews

Loading reviews…