CVE-2026-43049

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-01. 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:

HID: logitech-hidpp: Prevent use-after-free on force feedback initialisation failure

Presently, if the force feedback initialisation fails when probing the Logitech G920 Driving Force Racing Wheel for Xbox One, an error number will be returned and propagated before the userspace infrastructure (sysfs and /dev/input) has been torn down. If userspace ignores the errors and continues to use its references to these dangling entities, a UAF will promptly follow.

We have 2 options; continue to return the error, but ensure that all of the infrastructure is torn down accordingly or continue to treat this condition as a warning by emitting the message but returning success. It is thought that the original author's intention was to emit the warning but keep the device functional, less the force feedback feature, so let's go with that.

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

Published

May 1, 2026

Last Modified

May 7, 2026

Advisory Details (4)

Auto-updated May 7, 2026
No patch confirmed yet.
generic

HID: logitech-hidpp: Prevent use-after-free on force feedback initialisation failure - kernel/git/stable/linux.git - Linux kernel stable tree

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

HID: logitech-hidpp: Prevent use-after-free on force feedback initialisation failure - kernel/git/stable/linux.git - Linux kernel stable tree

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

HID: logitech-hidpp: Prevent use-after-free on force feedback initialisation failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9a793ac19eb84f44ed759c0fce80cf29bc2a2453
generic

HID: logitech-hidpp: Prevent use-after-free on force feedback initialisation failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/772f99cc8d6e5d95613bce93c9624e154c1abe88

Vendor Advisories for CVE-2026-43049(1)

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

Patch Availability(15)

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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 7.2~rc5-1~exp1 (335 versions)
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

(14)

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-43049?
CVE-2026-43049 is a high vulnerability published on May 1, 2026. In the Linux kernel, the following vulnerability has been resolved: HID: logitech-hidpp: Prevent use-after-free on force feedback initialisation failure Presently, if the force feedback initialisation fails when probing the Logitech G920 Driving Force Racing Wheel for Xbox One, an error number will…
When was CVE-2026-43049 disclosed?
CVE-2026-43049 was first published in the National Vulnerability Database on May 1, 2026, with the most recent update on May 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43049 actively exploited?
CVE-2026-43049 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 98.2% of all scored CVEs.
What is the CVSS score of CVE-2026-43049?
CVE-2026-43049 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-43049?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43049, 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-43049

Explore →

Is Your Infrastructure Affected by CVE-2026-43049?

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