CVE-2022-49826

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

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

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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

ata: libata-transport: fix double ata_host_put() in ata_tport_add()

In the error path in ata_tport_add(), when calling put_device(), ata_tport_release() is called, it will put the refcount of 'ap->host'.

And then ata_host_put() is called again, the refcount is decreased to 0, ata_host_release() is called, all ports are freed and set to null.

When unbinding the device after failure, ata_host_stop() is called to release the resources, it leads a null-ptr-deref(), because all the ports all freed and null.

Unable to handle kernel NULL pointer dereference at virtual address 0000000000000008 CPU: 7 PID: 18671 Comm: modprobe Kdump: loaded Tainted: G E 6.1.0-rc3+ #8 pstate: 80400009 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : ata_host_stop+0x3c/0x84 [libata] lr : release_nodes+0x64/0xd0 Call trace: ata_host_stop+0x3c/0x84 [libata] release_nodes+0x64/0xd0 devres_release_all+0xbc/0x1b0 device_unbind_cleanup+0x20/0x70 really_probe+0x158/0x320 __driver_probe_device+0x84/0x120 driver_probe_device+0x44/0x120 __driver_attach+0xb4/0x220 bus_for_each_dev+0x78/0xdc driver_attach+0x2c/0x40 bus_add_driver+0x184/0x240 driver_register+0x80/0x13c __pci_register_driver+0x4c/0x60 ahci_pci_driver_init+0x30/0x1000 [ahci]

Fix this by removing redundant ata_host_put() in the error path.

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
13%
KEV
Not listed

Published

May 1, 2025

Last Modified

August 5, 2026

Advisory Details (6)

Auto-updated Aug 4, 2026
No patch confirmed yet.
generic

ata: libata-transport: fix double ata_host_put() in ata_tport_add() - kernel/git/stable/linux.git - Linux kernel stable tree

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

ata: libata-transport: fix double ata_host_put() in ata_tport_add() - kernel/git/stable/linux.git - Linux kernel stable tree

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

ata: libata-transport: fix double ata_host_put() in ata_tport_add() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8c76310740807ade5ecdab5888f70ecb6d35732e
generic

ata: libata-transport: fix double ata_host_put() in ata_tport_add() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/865a6da40ba092c18292ae5f6194756131293745
generic

ata: libata-transport: fix double ata_host_put() in ata_tport_add() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/377ff82c33c0cb74562a353361b64b33c09562cf
generic

ata: libata-transport: fix double ata_host_put() in ata_tport_add() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/30e12e2be27ac6c4be2af4163c70db381364706f

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 4.19.267—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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (22 versions)5.10.158-1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux—6.0.10-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux—6.0.10-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux—6.0.10-1—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 4× in last 7d / 24× 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 153 total refreshes for this CVE.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2022-49826?
CVE-2022-49826 is a high vulnerability published on May 1, 2025. In the Linux kernel, the following vulnerability has been resolved: ata: libata-transport: fix double atahostput() in atatportadd() In the error path in atatportadd(), when calling put_device(), atatportrelease() is called, it will put the refcount of 'ap->host'. And then atahostput() is called…
When was CVE-2022-49826 disclosed?
CVE-2022-49826 was first published in the National Vulnerability Database on May 1, 2025, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-49826 actively exploited?
CVE-2022-49826 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.0% of all scored CVEs.
What is the CVSS score of CVE-2022-49826?
CVE-2022-49826 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2022-49826?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-49826, 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-2022-49826

Explore →

Is Your Infrastructure Affected by CVE-2022-49826?

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

Start Free Scan →Browse All CVEs