In the Linux kernel, the following vulnerability has been resolved:
s390/dasd: fix double module refcount decrement
Once the discipline is associated with the device, deleting the device
takes care of decrementing the module's refcount. Doing it manually on
this error path causes refcount to artificially decrease on each error
while it should just stay the same.
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel issue in the s390 DASD storage driver. A local user could trigger an error path that incorrectly decreases a module reference count, potentially causing a denial of service. The CVSS score is 5.5, with availability impact only. No source provided indicates active exploitation.
Executive priority
Treat as a routine but real availability risk for s390 Linux environments. It is not remotely exploitable based on provided data, but shared or multi-user mainframe Linux systems should receive normal kernel patch priority.
Technical view
CVE-2024-27054 fixes a double module refcount decrement in s390/dasd. After a discipline is associated with a device, device deletion already decrements the module refcount. A manual decrement on an error path can reduce the refcount incorrectly. CVSS is AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H.
Likely exposure
Exposure is mainly Linux systems on s390/IBM Z using the DASD subsystem. The attack vector is local and requires low privileges. Systems not running the affected s390 DASD code path are less likely to be exposed, but the provided source data does not fully clarify distribution-specific affected packages.
Exploitation context
The CVE record indicates local, low-complexity exploitation with no user interaction and high availability impact. It does not indicate confidentiality or integrity impact. KEV is false in the provided data, and no cited source states active exploitation.
Researcher notes
The source data names Linux kernel s390/dasd and provides stable commit references, but affected-version formatting is incomplete for precise distro mapping. No CWE is listed. Validate against upstream commits and downstream vendor kernels rather than relying only on generic version numbers.
Mitigation direction
Apply Linux kernel updates from your distribution that include the s390/dasd refcount fix.
For custom kernels, review and backport the referenced stable kernel commits.
Prioritize affected s390 systems where local users or workloads are not fully trusted.
Check vendor advisories for exact package names and fixed build numbers.
Validation and detection
Inventory Linux systems running on s390/IBM Z architecture.
Identify systems using the DASD storage driver or related modules.
Check kernel package changelogs for CVE-2024-27054 or the referenced commits.
Confirm running kernels include the relevant stable fix.
Monitor vendor security advisories for distribution-specific affected and fixed versions.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2024-27054 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.