CVE-2024-43900

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2024-08-26. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

media: xc2028: avoid use-after-free in load_firmware_cb()

syzkaller reported use-after-free in load_firmware_cb() [1]. The reason is because the module allocated a struct tuner in tuner_probe(), and then the module initialization failed, the struct tuner was released. A worker which created during module initialization accesses this struct tuner later, it caused use-after-free.

The process is as follows:

task-6504 worker_thread tuner_probe <= alloc dvb_frontend [2] ... request_firmware_nowait <= create a worker ... tuner_remove <= free dvb_frontend ... request_firmware_work_func <= the firmware is ready load_firmware_cb <= but now the dvb_frontend has been freed

To fix the issue, check the dvd_frontend in load_firmware_cb(), if it is null, report a warning and just return.

[1]: ================================================================== BUG: KASAN: use-after-free in load_firmware_cb+0x1310/0x17a0 Read of size 8 at addr ffff8000d7ca2308 by task kworker/2:3/6504

Call trace: load_firmware_cb+0x1310/0x17a0 request_firmware_work_func+0x128/0x220 process_one_work+0x770/0x1824 worker_thread+0x488/0xea0 kthread+0x300/0x430 ret_from_fork+0x10/0x20

Allocated by task 6504: kzalloc tuner_probe+0xb0/0x1430 i2c_device_probe+0x92c/0xaf0 really_probe+0x678/0xcd0 driver_probe_device+0x280/0x370 __device_attach_driver+0x220/0x330 bus_for_each_drv+0x134/0x1c0 __device_attach+0x1f4/0x410 device_initial_probe+0x20/0x30 bus_probe_device+0x184/0x200 device_add+0x924/0x12c0 device_register+0x24/0x30 i2c_new_device+0x4e0/0xc44 v4l2_i2c_new_subdev_board+0xbc/0x290 v4l2_i2c_new_subdev+0xc8/0x104 em28xx_v4l2_init+0x1dd0/0x3770

Freed by task 6504: kfree+0x238/0x4e4 tuner_remove+0x144/0x1c0 i2c_device_remove+0xc8/0x290 __device_release_driver+0x314/0x5fc device_release_driver+0x30/0x44 bus_remove_device+0x244/0x490 device_del+0x350/0x900 device_unregister+0x28/0xd0 i2c_unregister_device+0x174/0x1d0 v4l2_device_unregister+0x224/0x380 em28xx_v4l2_init+0x1d90/0x3770

The buggy address belongs to the object at ffff8000d7ca2000 which belongs to the cache kmalloc-2k of size 2048 The buggy address is located 776 bytes inside of 2048-byte region [ffff8000d7ca2000, ffff8000d7ca2800) The buggy address belongs to the page: page:ffff7fe00035f280 count:1 mapcount:0 mapping:ffff8000c001f000 index:0x0 flags: 0x7ff800000000100(slab) raw: 07ff800000000100 ffff7fe00049d880 0000000300000003 ffff8000c001f000 raw: 0000000000000000 0000000080100010 00000001ffffffff 0000000000000000 page dumped because: kasan: bad access detected

Memory state around the buggy address: ffff8000d7ca2200: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ffff8000d7ca2280: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb >ffff8000d7ca2300: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ^ ffff8000d7ca2380: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ffff8000d7ca2400: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ==================================================================

[2] Actually, it is allocated for struct tuner, and dvb_frontend is inside.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
35(Track)
EG Risk 35/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
Severity78% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
12%
KEV
Not listed

Published

August 26, 2024

Last Modified

November 3, 2025

References (5)

Patch Availability(31)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-16.04-edge (4.15.0.235.247~16.04.1) @ xenial2026-05-23ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1020.23~22.04.1) @ jammy2026-05-23ubuntu
ubuntulinux-virtual-lts-xenial (4.4.0.266.272) @ xenial2026-05-23ubuntu
ubuntulinux-virtual (3.13.0.204.214) @ trusty2026-05-23ubuntu
ubuntulinux-virtual-hwe-24.04 (6.8.0-50.51) @ noble2026-05-23ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k (6.8.0-1019.21.1) @ noble2026-05-23ubuntu
ubuntulinux-tools-gkeop-6.8 (6.8.0-1002.4) @ noble2026-05-23ubuntu
ubuntulinux-tools-azure-lts-18.04 (4.15.0.1186.154) @ bionic2026-05-23ubuntu
ubuntulinux-virtual-lts-xenial (4.4.0.266.300~14.04.1) @ trusty2026-05-23ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-50.51~22.04.1) @ jammy2026-05-23ubuntu
ubuntulinux-tools-oracle (4.15.0.1140.151~16.04.1) @ xenial2026-05-23ubuntu
ubuntulinux-tools-kvm (4.4.0.1142.139) @ xenial2026-05-23ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.135.133) @ jammy2026-05-23ubuntu
ubuntulinux-xilinx-zynqmp-tools-host (5.15.0-1044.48) @ jammy2026-05-23ubuntu
ubuntulinux-tools-gcp-fips (5.15.0.1079.69) @ jammy2026-05-23ubuntu
ubuntulinux-tools-nvidia-tegra-rt (5.15.0.1033.33) @ jammy2026-05-23ubuntu
ubuntulinux-tools-kvm (5.15.0.1076.72) @ jammy2026-05-23ubuntu
ubuntulinux-tools-realtime (5.15.0.1080.83) @ jammy2026-05-23ubuntu
ubuntulinux-virtual-hwe-18.04-edge (5.4.0.211.206) @ focal2026-05-23ubuntu
ubuntulinux-tools-fips (5.4.0.1116.113) @ focal2026-05-23ubuntu
ubuntulinux-tools-aws-edge (5.4.0.1142.152~18.04.1) @ bionic2026-05-23ubuntu
ubuntulinux-tools-aws-lts-20.04 (5.4.0.1142.139) @ focal2026-05-23ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.136.147~20.04.1) @ focal2026-05-23ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.4.0-1060 (5.4.0-1060.64) @ focal2026-05-23ubuntu
ubuntulinux-tools-ibm-edge (5.4.0.1090.95~18.04.1) @ bionic2026-05-23ubuntu
ubuntulinux-tools-raspi2-hwe-18.04-edge (5.4.0.1129.160) @ focal2026-05-23ubuntu
ubuntulinux-tools-raspi-hwe-18.04-edge (5.4.0.1129.142~18.04.1) @ bionic2026-05-23ubuntu
ubuntulinux-tools-gcp-edge (5.15.0.1081.90~20.04.1) @ focal2026-05-23ubuntu
ubuntulinux-tools-gcp-fips (5.4.0.1145.87) @ focal2026-05-23ubuntu
ubuntulinux-tools-aws-fips (5.4.0.1142.89) @ focal2026-05-23ubuntu
linuxKernel @ 6.1.105—osv

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 ... 7.2~rc5-1~exp1 (496 versions)——
linux-6.16.1.106-3~deb11u1, 6.1.106-3~deb11u2, 6.1.106-3~deb11u3, 6.1.112-1~deb11u16.1.119-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.27-1 ... 6.1.99-1 (26 versions)6.1.106-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux—6.10.6-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux—6.10.6-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 9× in last 7d / 30× 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 166 total refreshes for this CVE.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2024-43900?
CVE-2024-43900 is a high vulnerability published on August 26, 2024. In the Linux kernel, the following vulnerability has been resolved: media: xc2028: avoid use-after-free in loadfirmwarecb() syzkaller reported use-after-free in loadfirmwarecb() [1]. The reason is because the module allocated a struct tuner in tuner_probe(), and then the module initialization…
When was CVE-2024-43900 disclosed?
CVE-2024-43900 was first published in the National Vulnerability Database on August 26, 2024, with the most recent update on November 3, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-43900 actively exploited?
CVE-2024-43900 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 87.9% of all scored CVEs.
What is the CVSS score of CVE-2024-43900?
CVE-2024-43900 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2024-43900?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-43900, 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-2024-43900

Explore →

Is Your Infrastructure Affected by CVE-2024-43900?

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

Start Free Scan →Browse All CVEs