CVE-2026-45981

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 5 sources updated this week
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:

s390/cio: Fix device lifecycle handling in css_alloc_subchannel()

css_alloc_subchannel() calls device_initialize() before setting up the DMA masks. If dma_set_coherent_mask() or dma_set_mask() fails, the error path frees the subchannel structure directly, bypassing the device model reference counting.

Once device_initialize() has been called, the embedded struct device must be released via put_device(), allowing the release callback to free the container structure.

Fix the error path by dropping the initial device reference with put_device() instead of calling kfree() directly.

This ensures correct device lifetime handling and avoids potential use-after-free or double-free issues.

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 27, 2026

Last Modified

June 16, 2026

Advisory Details (5)

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

s390/cio: Fix device lifecycle handling in css_alloc_subchannel() - kernel/git/stable/linux.git - Linux kernel stable tree

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

s390/cio: Fix device lifecycle handling in css_alloc_subchannel() - kernel/git/stable/linux.git - Linux kernel stable tree

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

s390/cio: Fix device lifecycle handling in css_alloc_subchannel() - kernel/git/stable/linux.git - Linux kernel stable tree

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

s390/cio: Fix device lifecycle handling in css_alloc_subchannel() - kernel/git/stable/linux.git - Linux kernel stable tree

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

s390/cio: Fix device lifecycle handling in css_alloc_subchannel() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6715560527e343a387e4a0d2e6c401748e89fa55

Vendor Advisories for CVE-2026-45981(1)

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

Patch Availability(13)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-6.8 (6.8.0-134.134) @ noble2026-09-14ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1058.61.1) @ noble2026-09-14ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1029.30) @ noble2026-09-14ubuntu
ubuntulinux-tools-lowlatency-hwe-22.04-edge (6.8.0-134.134.1~22.04.1) @ jammy2026-09-14ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1032.33) @ noble2026-09-14ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2049.50) @ noble2026-09-14ubuntu
ubuntulinux-tools-raspi-6.8 (6.8.0-1060.64) @ noble2026-09-14ubuntu
ubuntulinux-tools-fips-6.8 (6.8.0-134.134+fips1) @ noble2026-09-14ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1063.71) @ noble2026-09-14ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-09-14ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-09-14ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-09-14ubuntu
linuxKernel @ 6.6.128—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 ... 7.2~rc5-1~exp1 (496 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (350 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.18~rc7-1~exp1 (103 versions)6.18.14-1—

Weakness Classification(1)

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

All Vendor Advisories

(12)

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 / 39× 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 203 total refreshes for this CVE.

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

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

Frequently asked(5)

What is CVE-2026-45981?
CVE-2026-45981 is a medium vulnerability published on May 27, 2026. In the Linux kernel, the following vulnerability has been resolved: s390/cio: Fix device lifecycle handling in cssallocsubchannel() cssallocsubchannel() calls device_initialize() before setting up the DMA masks. If dmasetcoherentmask() or dmaset_mask() fails, the error path frees the subchannel…
When was CVE-2026-45981 disclosed?
CVE-2026-45981 was first published in the National Vulnerability Database on May 27, 2026, with the most recent update on June 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-45981 actively exploited?
CVE-2026-45981 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.4% of all scored CVEs.
What is the CVSS score of CVE-2026-45981?
CVE-2026-45981 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-45981?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-45981, 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-45981

Explore →

Is Your Infrastructure Affected by CVE-2026-45981?

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

Start Free Scan →Browse All CVEs