CVE-2026-23306

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

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

scsi: pm8001: Fix use-after-free in pm8001_queue_command()

Commit e29c47fe8946 ("scsi: pm8001: Simplify pm8001_task_exec()") refactors pm8001_queue_command(), however it introduces a potential cause of a double free scenario when it changes the function to return -ENODEV in case of phy down/device gone state.

In this path, pm8001_queue_command() updates task status and calls task_done to indicate to upper layer that the task has been handled. However, this also frees the underlying SAS task. A -ENODEV is then returned to the caller. When libsas sas_ata_qc_issue() receives this error value, it assumes the task wasn't handled/queued by LLDD and proceeds to clean up and free the task again, resulting in a double free.

Since pm8001_queue_command() handles the SAS task in this case, it should return 0 to the caller indicating that the task has been handled.

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

Published

March 25, 2026

Last Modified

August 5, 2026

Advisory Details (6)

Auto-updated Jun 10, 2026
No patch confirmed yet.
generic

scsi: pm8001: Fix use-after-free in pm8001_queue_command() - kernel/git/stable/linux.git - Linux kernel stable tree

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

scsi: pm8001: Fix use-after-free in pm8001_queue_command() - kernel/git/stable/linux.git - Linux kernel stable tree

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

scsi: pm8001: Fix use-after-free in pm8001_queue_command() - kernel/git/stable/linux.git - Linux kernel stable tree

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

scsi: pm8001: Fix use-after-free in pm8001_queue_command() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/824a7672e3540962d5c77d4c6666254d7aa6f0b3
generic

scsi: pm8001: Fix use-after-free in pm8001_queue_command() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/38353c26db28efd984f51d426eac2396d299cca7
generic

scsi: pm8001: Fix use-after-free in pm8001_queue_command() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/227ff4af00abc40b95123cc27ee8079069dcd8d7

Vendor Advisories for CVE-2026-23306(2)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 6.1.167—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
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 (117 versions)6.19.8-1—

Weakness Classification(1)

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

Additional Vendor Advisories

(13)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 6× in last 7d / 57× 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 213 total refreshes for this CVE.

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

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

Frequently asked(5)

What is CVE-2026-23306?
CVE-2026-23306 is a high vulnerability published on March 25, 2026. In the Linux kernel, the following vulnerability has been resolved: scsi: pm8001: Fix use-after-free in pm8001queuecommand() Commit e29c47fe8946 ("scsi: pm8001: Simplify pm8001taskexec()") refactors pm8001queuecommand(), however it introduces a potential cause of a double free scenario when it…
When was CVE-2026-23306 disclosed?
CVE-2026-23306 was first published in the National Vulnerability Database on March 25, 2026, 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-2026-23306 actively exploited?
CVE-2026-23306 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.5% of all scored CVEs.
What is the CVSS score of CVE-2026-23306?
CVE-2026-23306 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-23306?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-23306, 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-23306

Explore →

Is Your Infrastructure Affected by CVE-2026-23306?

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

Start Free Scan →Browse All CVEs