CVE-2026-43035

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-05-01. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

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 v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

May 1, 2026

Last Modified

July 14, 2026

Advisory Details (10)

Auto-updated Jul 14, 2026
⚠️ Active exploitation confirmed. No patch confirmed yet.
generic

net: sched: cls_api: fix tc_chain_fill_node to initialize tcm_info to zero to prevent an info-leak - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e6e3eb5ee89ac4c163d46429391c889a1bb5e404
generic

net: sched: cls_api: fix tc_chain_fill_node to initialize tcm_info to zero to prevent an info-leak - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e35f5195cd44ff4053fbc5d71ea97681728a0099
generic

net: sched: cls_api: fix tc_chain_fill_node to initialize tcm_info to zero to prevent an info-leak - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d6db08484c6cb3d4ad696246f9d288eceba2a078
generic

net: sched: cls_api: fix tc_chain_fill_node to initialize tcm_info to zero to prevent an info-leak - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/906997ea3766c24fbbf9cc4bf17c047315bbd138
generic

net: sched: cls_api: fix tc_chain_fill_node to initialize tcm_info to zero to prevent an info-leak - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/903c3405cfcc7700260e456ab66a5867586c9e69
generic

net: sched: cls_api: fix tc_chain_fill_node to initialize tcm_info to zero to prevent an info-leak - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/71a3eda7e850ae844cb8993065f4e410c11a46ce
generic

net: sched: cls_api: fix tc_chain_fill_node to initialize tcm_info to zero to prevent an info-leak - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4ae5d23f51fb91d7d1140c6f1ba77ab0756054c3
generic

net: sched: cls_api: fix tc_chain_fill_node to initialize tcm_info to zero to prevent an info-leak - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1091b3c174441a52fdbb92e2fe00338f9371a91c

Vendor Advisories for CVE-2026-43035(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(27)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1064.72+fips1) @ noble2026-08-23ubuntu
ubuntulinux-tools-nvidia-hwe-22.04-edge (6.8.0-1059.62~22.04.1) @ jammy2026-08-23ubuntu
ubuntulinux-tools-oracle-edge (6.8.0-1058.61~22.04.1) @ jammy2026-08-23ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2050.52) @ noble2026-08-23ubuntu
ubuntulinux-virtual-6.8 (6.8.0-136.136) @ noble2026-08-23ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1058.61) @ noble2026-08-23ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.66~20.04.1) @ focal2026-08-23ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.64) @ jammy2026-08-23ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1075 (5.15.0-1075.79) @ jammy2026-08-23ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1109.115~20.04.1) @ focal2026-08-23ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-08-23ubuntu
ubuntulinux-tools-nvidia-lowlatency-5.15 (5.15.0.1107.107) @ jammy2026-08-23ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1117.102) @ jammy2026-08-23ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1033.34) @ noble2026-08-23ubuntu
ubuntulinux-tools-ibm-edge (5.15.0.1106.110~20.04.1) @ focal2026-08-23ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1063.71~22.04.1) @ jammy2026-08-23ubuntu
ubuntulinux-tools-aws-lts-24.04 (6.8.0-1061.64+1) @ noble2026-08-23ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-08-23ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1063.71+fips2) @ noble2026-08-23ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-08-23ubuntu
ubuntulinux-tools-oracle-lts-22.04 (5.15.0.1109.105) @ jammy2026-08-23ubuntu
ubuntulinux-tools-intel-iot-realtime-5.15 (5.15.0.1104.108) @ jammy2026-08-23ubuntu
ubuntulinux-tools-azure-fde-lts-22.04 (5.15.0.1117.126) @ jammy2026-08-23ubuntu
ubuntulinux-tools-aws-fips-6.8 (6.8.0-1061.64+fips1) @ noble2026-08-23ubuntu
ubuntulinux-tools-gcp-edge (5.15.0.1112.122~20.04.1) @ focal2026-08-23ubuntu
ubuntulinux-tools-intel-iotg-5.15 (5.15.0.1107.106) @ jammy2026-08-23ubuntu
linuxKernel @ 5.10.253osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (53 versions)5.10.257-1
linux-6.16.1.106-3~deb11u1 ... 6.1.164-1~deb11u1 (16 versions)6.1.170-1~deb11u1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (48 versions)6.1.170-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (122 versions)6.19.12-1

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(25)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 4× in last 7d / 56× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 175 total refreshes for this CVE.

  1. 2026-09-04 05:06 UTCEPSS rescore
  2. 2026-09-01 13:54 UTCEPSS rescore
  3. 2026-08-30 19:17 UTCEPSS rescore
  4. 2026-08-30 01:22 UTCEPSS rescore
  5. 2026-08-28 21:41 UTCEPSS rescore
  6. 2026-08-27 14:25 UTCEPSS rescore
  7. 2026-08-26 14:46 UTCEPSS rescore
  8. 2026-08-25 13:49 UTCEPSS rescore
  9. 2026-08-23 21:50 UTCEG score recompute
  10. 2026-08-23 21:50 UTCVendor advisory
  11. 2026-08-23 21:50 UTCGHSA enrichment
  12. 2026-08-21 23:49 UTCEPSS rescore
  13. 2026-08-20 22:55 UTCEPSS rescore
  14. 2026-08-19 17:03 UTCEPSS rescore
  15. 2026-08-18 13:48 UTCEPSS rescore
  16. 2026-08-17 13:47 UTCEPSS rescore
  17. 2026-08-17 13:21 UTCEG score recompute
  18. 2026-08-17 13:21 UTCVendor advisory
  19. 2026-08-17 13:21 UTCGHSA enrichment
  20. 2026-08-16 14:56 UTCEPSS rescore
  21. 2026-08-16 05:16 UTCEG score recompute
  22. 2026-08-16 05:16 UTCVendor advisory
  23. 2026-08-16 05:16 UTCGHSA enrichment
  24. 2026-08-16 02:14 UTCEPSS rescore
  25. 2026-08-15 01:30 UTCEPSS rescore
Show 75 more
  1. 2026-08-14 03:44 UTCEG score recompute
  2. 2026-08-14 03:44 UTCVendor advisory
  3. 2026-08-14 03:44 UTCGHSA enrichment
  4. 2026-08-13 22:00 UTCEPSS rescore
  5. 2026-08-13 00:12 UTCEG score recompute
  6. 2026-08-13 00:12 UTCVendor advisory
  7. 2026-08-13 00:12 UTCGHSA enrichment
  8. 2026-08-12 13:51 UTCEPSS rescore
  9. 2026-08-12 00:59 UTCEG score recompute
  10. 2026-08-12 00:59 UTCVendor advisory
  11. 2026-08-12 00:59 UTCGHSA enrichment
  12. 2026-08-11 13:43 UTCEPSS rescore
  13. 2026-08-11 01:47 UTCEG score recompute
  14. 2026-08-11 01:47 UTCVendor advisory
  15. 2026-08-11 01:47 UTCGHSA enrichment
  16. 2026-08-11 00:00 UTCEPSS rescore
  17. 2026-08-10 02:05 UTCEG score recompute
  18. 2026-08-10 02:05 UTCVendor advisory
  19. 2026-08-10 02:05 UTCGHSA enrichment
  20. 2026-08-09 13:46 UTCEPSS rescore
  21. 2026-08-09 02:52 UTCEG score recompute
  22. 2026-08-09 02:52 UTCVendor advisory
  23. 2026-08-09 02:52 UTCGHSA enrichment
  24. 2026-08-08 16:37 UTCEPSS rescore
  25. 2026-08-07 21:00 UTCEG score recompute
  26. 2026-08-07 21:00 UTCVendor advisory
  27. 2026-08-07 21:00 UTCGHSA enrichment
  28. 2026-08-06 21:48 UTCEG score recompute
  29. 2026-08-06 21:48 UTCVendor advisory
  30. 2026-08-06 21:48 UTCGHSA enrichment
  31. 2026-08-06 13:46 UTCEPSS rescore
  32. 2026-08-05 22:35 UTCEG score recompute
  33. 2026-08-05 22:35 UTCVendor advisory
  34. 2026-08-05 22:35 UTCGHSA enrichment
  35. 2026-08-05 19:17 UTCEPSS rescore
  36. 2026-08-04 15:10 UTCEPSS rescore
  37. 2026-08-04 10:38 UTCEPSS rescore
  38. 2026-08-03 20:18 UTCEG score recompute
  39. 2026-08-03 20:18 UTCVendor advisory
  40. 2026-08-03 20:18 UTCGHSA enrichment
  41. 2026-08-03 10:36 UTCEPSS rescore
  42. 2026-08-02 05:38 UTCEG score recompute
  43. 2026-08-02 05:38 UTCVendor advisory
  44. 2026-08-02 05:38 UTCGHSA enrichment
  45. 2026-08-02 02:27 UTCEPSS rescore
  46. 2026-08-01 04:16 UTCEPSS rescore
  47. 2026-07-30 16:28 UTCEPSS rescore
  48. 2026-07-30 01:30 UTCEPSS rescore
  49. 2026-07-28 15:36 UTCEPSS rescore
  50. 2026-07-27 14:13 UTCEPSS rescore
  51. 2026-07-26 14:54 UTCEPSS rescore
  52. 2026-07-26 14:54 UTCEPSS rescore
  53. 2026-07-25 14:18 UTCEPSS rescore
  54. 2026-07-24 14:17 UTCEPSS rescore
  55. 2026-07-23 14:18 UTCEPSS rescore
  56. 2026-07-23 03:13 UTCEG score recompute
  57. 2026-07-22 14:08 UTCEPSS rescore
  58. 2026-07-21 15:24 UTCEPSS rescore
  59. 2026-07-20 17:08 UTCEPSS rescore
  60. 2026-07-19 19:18 UTCOSV refresh
  61. 2026-07-19 14:31 UTCEPSS rescore
  62. 2026-07-19 02:29 UTCEPSS rescore
  63. 2026-07-18 10:04 UTCEPSS rescore
  64. 2026-07-16 17:03 UTCEPSS rescore
  65. 2026-07-15 16:57 UTCEPSS rescore
  66. 2026-07-15 02:00 UTCEPSS rescore
  67. 2026-07-14 13:19 UTCNVD updateCVSS v3 → 5.5 · severity → MEDIUM
  68. 2026-07-14 13:11 UTCMITRE cvelistV5
  69. 2026-07-13 22:30 UTCEPSS rescore
  70. 2026-07-13 06:13 UTCEPSS rescore
  71. 2026-07-12 05:46 UTCEPSS rescore
  72. 2026-07-11 08:27 UTCEPSS rescore
  73. 2026-07-09 19:10 UTCEPSS rescore
  74. 2026-07-08 15:16 UTCEPSS rescore
  75. 2026-07-07 13:46 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-43035?
CVE-2026-43035 is a medium vulnerability published on May 1, 2026. In the Linux kernel, the following vulnerability has been resolved: net: sched: clsapi: fix tcchainfillnode to initialize tcm_info to zero to prevent an info-leak When building netlink messages, tcchainfill_node() never initializes the tcm_info field of struct tcmsg. Since the allocation is not…
When was CVE-2026-43035 disclosed?
CVE-2026-43035 was first published in the National Vulnerability Database on May 1, 2026, with the most recent update on July 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43035 actively exploited?
CVE-2026-43035 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.2% of all scored CVEs.
What is the CVSS score of CVE-2026-43035?
CVE-2026-43035 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-43035?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43035, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-43035

Explore →

Is Your Infrastructure Affected by CVE-2026-43035?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.