Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2024-56699: s390/pci: Fix potential double remove of hotplug slot

Noroxi assessment

Priority: Monitor (action score 31/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 371bd905599d18da62d75e3974acbf6a41e315c7, c1489651071ab1be46d2af1da8adb15c9fc3c069, c4a585e952ca403a370586d3f16e8331a7564901.

Low priority for now. Upgrade to Linux Linux 371bd905599d18da62d75e3974acbf6a41e315c7, c1489651071ab1be46d2af1da8adb15c9fc3c069, c4a585e952ca403a370586d3f16e8331a7564901 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In the Linux kernel, the following vulnerability has been resolved: s390/pci: Fix potential double remove of hotplug slot In commit 6ee600bfbe0f ("s390/pci: remove hotplug slot when releasing the device") the zpci_exit_slot() was moved from zpci_device_reserved() to zpci_release_device() with the intention of keeping the hotplug slot around until the device is actually removed. Now zpci_release_device() is only called once all references are dropped. Since the zPCI subsystem only drops its reference once the device is in the reserved state it follows that zpci_release_device() must only deal with devices in the reserved state. Despite that it contains code to tear down from both configured and standby state. For the standby case this already includes the removal of the hotplug slot so would cause a double removal if a device was ever removed in either configured or standby state. Instead of causing a potential double removal in a case that should never happen explicitly WARN_ON() if a device in non-reserved state is released and get rid of the dead code cases.

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
Dec 28, 2024
Updated
Jun 17, 2026
EPSS
0.2% · 11th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-56699

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel6.9 and later · before 6.11.11
  • linux linux kernel6.12 and later · before 6.12.2

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 6.9affected
    • 6ee600bfbe0f818ffb7748d99e9b0c89d0d9f02a and later · before c1489651071ab1be46d2af1da8adb15c9fc3c069affected · git
    • 6ee600bfbe0f818ffb7748d99e9b0c89d0d9f02a and later · before 371bd905599d18da62d75e3974acbf6a41e315c7affected · git
    • 6ee600bfbe0f818ffb7748d99e9b0c89d0d9f02a and later · before c4a585e952ca403a370586d3f16e8331a7564901affected · git
    • before 6.9not affected · semver
    • 6.11.11 and later · up to and including 6.11.*not affected · semver
    • 6.12.2 and later · up to and including 6.12.*not affected · semver
    • 6.13 and laternot affected · original_commit_for_fix

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:13linuxbefore 6.12.3-16.12.3-1
openSUSE:Leap 15.6dtb-aarch64before 6.4.0-150600.23.60.36.4.0-150600.23.60.3
openSUSE:Leap 15.6kernel-64kbbefore 6.4.0-150600.23.60.46.4.0-150600.23.60.4
openSUSE:Leap 15.6kernel-azurebefore 6.4.0-150600.8.43.16.4.0-150600.8.43.1
openSUSE:Leap 15.6kernel-debugbefore 6.4.0-150600.23.60.46.4.0-150600.23.60.4
openSUSE:Leap 15.6kernel-defaultbefore 6.4.0-150600.23.60.56.4.0-150600.23.60.5
openSUSE:Leap 15.6kernel-default-basebefore 6.4.0-150600.23.60.5.150600.12.26.46.4.0-150600.23.60.5.150600.12.26.4
openSUSE:Leap 15.6kernel-docsbefore 6.4.0-150600.23.60.36.4.0-150600.23.60.3
openSUSE:Leap 15.6kernel-kvmsmallbefore 6.4.0-150600.23.60.46.4.0-150600.23.60.4
openSUSE:Leap 15.6kernel-obs-buildbefore 6.4.0-150600.23.60.36.4.0-150600.23.60.3
openSUSE:Leap 15.6kernel-obs-qabefore 6.4.0-150600.23.60.26.4.0-150600.23.60.2
openSUSE:Leap 15.6kernel-rtbefore 6.4.0-150600.10.44.16.4.0-150600.10.44.1
openSUSE:Leap 15.6kernel-rt_debugbefore 6.4.0-150600.10.44.16.4.0-150600.10.44.1
openSUSE:Leap 15.6kernel-sourcebefore 6.4.0-150600.23.60.46.4.0-150600.23.60.4
openSUSE:Leap 15.6kernel-source-azurebefore 6.4.0-150600.8.43.16.4.0-150600.8.43.1
openSUSE:Leap 15.6kernel-source-rtbefore 6.4.0-150600.10.44.16.4.0-150600.10.44.1
openSUSE:Leap 15.6kernel-symsbefore 6.4.0-150600.23.60.46.4.0-150600.23.60.4
openSUSE:Leap 15.6kernel-syms-azurebefore 6.4.0-150600.8.43.16.4.0-150600.8.43.1
openSUSE:Leap 15.6kernel-syms-rtbefore 6.4.0-150600.10.44.16.4.0-150600.10.44.1
openSUSE:Leap 15.6kernel-zfcpdumpbefore 6.4.0-150600.23.60.46.4.0-150600.23.60.4
SUSE:Linux Enterprise Live Patching 15 SP6kernel-livepatch-SLE15-SP6_Update_13before 1-150600.13.6.41-150600.13.6.4
SUSE:Linux Enterprise Live Patching 15 SP6kernel-livepatch-SLE15-SP6-RT_Update_13before 1-150600.1.5.11-150600.1.5.1
SUSE:Linux Enterprise Live Patching 15 SP7kernel-livepatch-SLE15-SP7_Update_2before 1-150700.15.3.11-150700.15.3.1
SUSE:Linux Enterprise Live Patching 15 SP7kernel-livepatch-SLE15-SP7-RT_Update_2before 1-150700.1.5.11-150700.1.5.1

+39

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2024-56697Dec 28, 2024 · drm/amdgpu: Fix the memory allocation issue in amdgpu_discovery_get_nps_info()
    22Monitor
  • ← EarlierCVE-2024-56698Dec 28, 2024 · usb: dwc3: gadget: Fix looping of queued SG entries
    22Monitor
  • Later →CVE-2024-56700Dec 28, 2024 · media: wl128x: Fix atomicity violation in fmc_send_cmd()
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux371bd905599d18da62d75e3974acbf6a41e315c7Vendor (CNA)
Linux Linuxc1489651071ab1be46d2af1da8adb15c9fc3c069Vendor (CNA)
Linux Linuxc4a585e952ca403a370586d3f16e8331a7564901Vendor (CNA)
debian:linux6.12.3-1 · Debian:13Package registry (OSV)
opensuse:dtb-aarch646.4.0-150600.23.60.3 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-64kb6.4.0-150600.23.60.4 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-azure6.4.0-150600.8.43.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-debug6.4.0-150600.23.60.4 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-default6.4.0-150600.23.60.5 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-default-base6.4.0-150600.23.60.5.150600.12.26.4 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-rt6.4.0-150600.10.44.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-rt_debug6.4.0-150600.10.44.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-source-azure6.4.0-150600.8.43.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-source-rt6.4.0-150600.10.44.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-syms-azure6.4.0-150600.8.43.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-syms-rt6.4.0-150600.10.44.1 · openSUSE:Leap 15.6Package registry (OSV)
suse:kernel-64kb6.4.0-150700.53.6.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP7Package registry (OSV)
suse:kernel-azure6.4.0-150600.8.43.1 · SUSE:Linux Enterprise Module for Public Cloud 15 SP6Package registry (OSV)
suse:kernel-default6.4.0-150700.53.6.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP7Package registry (OSV)
suse:kernel-default-base6.4.0-150700.53.6.1.150700.17.6.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP7Package registry (OSV)
suse:kernel-docs6.4.0-150700.53.6.1 · SUSE:Linux Enterprise Module for Development Tools 15 SP7Package registry (OSV)
suse:kernel-livepatch-SLE15-SP6-RT_Update_131-150600.1.5.1 · SUSE:Linux Enterprise Live Patching 15 SP6Package registry (OSV)
suse:kernel-livepatch-SLE15-SP7_Update_21-150700.15.3.1 · SUSE:Linux Enterprise Live Patching 15 SP7Package registry (OSV)
suse:kernel-obs-build6.4.0-150700.53.6.1 · SUSE:Linux Enterprise Module for Development Tools 15 SP7Package registry (OSV)
suse:kernel-rt6.4.0-150600.10.44.1 · SUSE:Real Time Module 15 SP6Package registry (OSV)
suse:kernel-rt_debug6.4.0-150600.10.44.1 · SUSE:Real Time Module 15 SP6Package registry (OSV)
suse:kernel-source6.4.0-150700.53.6.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP7Package registry (OSV)
suse:kernel-source-azure6.4.0-150600.8.43.1 · SUSE:Linux Enterprise Module for Public Cloud 15 SP6Package registry (OSV)
suse:kernel-source-rt6.4.0-150600.10.44.1 · SUSE:Real Time Module 15 SP6Package registry (OSV)
suse:kernel-syms6.4.0-150700.53.6.1 · SUSE:Linux Enterprise Module for Development Tools 15 SP7Package registry (OSV)

+3

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-31608482 days apartsmb: server: avoid double-free in smb_direct_free_sendmsg after smb_direct_flush_send_list()
    39Monitor
  • CVE-2026-31609482 days apartsmb: client: avoid double-free in smbd_free_send_io() after smbd_send_batch_flush()
    39Monitor
  • CVE-2026-43011489 days apartnet/x25: Fix potential double free of skb
    39Monitor
  • CVE-2026-43414496 days apartscsi: qla2xxx: Completely fix fcport double free
    39Monitor
  • CVE-2024-35814225 days apartswiotlb: Fix double-allocation of slots due to broken alignment handling
    35Monitor
  • CVE-2026-43249494 days apart9p/xen: protect xen_9pfs_front_free against concurrent calls
    35Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-415 · Double Free

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (2 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records