Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-43035net: sched: cls_api: fix tc_chain_fill_node to initialize tcm_info to zero to prevent an info-leak

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 6 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-43035, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.13% · top 97% of all CVEs (15 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 32a4f5ecd7381f30ae3bb36dea77a150ba68af2e – < 903c3405cfcc7700260e456ab66a5867586c9e69
    • affected 32a4f5ecd7381f30ae3bb36dea77a150ba68af2e – < 71a3eda7e850ae844cb8993065f4e410c11a46ce
    • affected 32a4f5ecd7381f30ae3bb36dea77a150ba68af2e – < 4ae5d23f51fb91d7d1140c6f1ba77ab0756054c3
    • affected 32a4f5ecd7381f30ae3bb36dea77a150ba68af2e – < e35f5195cd44ff4053fbc5d71ea97681728a0099
    • affected 32a4f5ecd7381f30ae3bb36dea77a150ba68af2e – < d6db08484c6cb3d4ad696246f9d288eceba2a078
    • affected 32a4f5ecd7381f30ae3bb36dea77a150ba68af2e – < 906997ea3766c24fbbf9cc4bf17c047315bbd138
    • affected 32a4f5ecd7381f30ae3bb36dea77a150ba68af2e – < 1091b3c174441a52fdbb92e2fe00338f9371a91c
    • affected 32a4f5ecd7381f30ae3bb36dea77a150ba68af2e – < e6e3eb5ee89ac4c163d46429391c889a1bb5e404
  • Linux · Linux

    • affected 4.19
    • unaffected < 4.19
    • unaffected 5.10.253 – ≤ 5.10.*
    • unaffected 5.15.203 – ≤ 5.15.*
    • unaffected 6.1.168 – ≤ 6.1.*
    • unaffected 6.6.134 – ≤ 6.6.*
    • unaffected 6.12.81 – ≤ 6.12.*
    • unaffected 6.18.22 – ≤ 6.18.*
    • unaffected 6.19.12 – ≤ 6.19.*
    • unaffected 7.0 – ≤ *

References

References11

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-43035 badge
[![CVE-2026-43035](https://cveledger.app/badge/CVE-2026-43035.svg)](https://cveledger.app/cve/CVE-2026-43035)

Record last updated .