Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2024-56531: ALSA: caiaq: Use snd_card_free_when_closed() at disconnection

Noroxi assessment

Priority: Monitor (action score 22/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.22% (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 237f3faf0177bdde728fa3106d730d806436aa4d, 3993edf44d3df7b6e8c753eac6ac8783473fcbab, 4507a8b9b30344c5ddd8219945f446d47e966a6d.
  • Severity is disputed: the assigning authority (CNA) scores it 7.8, NVD 5.5.

Low priority for now. Upgrade to Linux Linux 237f3faf0177bdde728fa3106d730d806436aa4d, 3993edf44d3df7b6e8c753eac6ac8783473fcbab, 4507a8b9b30344c5ddd8219945f446d47e966a6d 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: ALSA: caiaq: Use snd_card_free_when_closed() at disconnection The USB disconnect callback is supposed to be short and not too-long waiting. OTOH, the current code uses snd_card_free() at disconnection, but this waits for the close of all used fds, hence it can take long. It eventually blocks the upper layer USB ioctls, which may trigger a soft lockup. An easy workaround is to replace snd_card_free() with snd_card_free_when_closed(). This variant returns immediately while the release of resources is done asynchronously by the card device release at the last close. This patch also splits the code to the disconnect and the free phases; the former is called immediately at the USB disconnect callback while the latter is called from the card destructor.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Dec 27, 2024
Updated
Aug 5, 2026
EPSS
0.2% · 13th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
5.5
CNA · Linux
7.8
2.3 point gap

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

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-56531

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 kernel2.6.22 and later · before 4.19.325
  • linux linux kernel4.20 and later · before 5.4.287
  • linux linux kernel5.5 and later · before 5.10.231
  • linux linux kernel5.11 and later · before 5.15.174
  • linux linux kernel5.16 and later · before 6.1.120
  • linux linux kernel6.2 and later · before 6.6.64
  • linux linux kernel6.7 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

    • 2.6.22affected
    • 523f1dce37434a9a6623bf46e7893e2b4b10ac3c and later · before 3993edf44d3df7b6e8c753eac6ac8783473fcbabaffected · git
    • 523f1dce37434a9a6623bf46e7893e2b4b10ac3c and later · before ebad462eec93b0f701dfe4de98990e7355283801affected · git
    • 523f1dce37434a9a6623bf46e7893e2b4b10ac3c and later · before 4dd821dcbfcecf7af6a08370b0b217cde2818acfaffected · git
    • 523f1dce37434a9a6623bf46e7893e2b4b10ac3c and later · before cadf1d8e9ddcd74584ec961aeac14ac549b261d8affected · git
    • 523f1dce37434a9a6623bf46e7893e2b4b10ac3c and later · before 237f3faf0177bdde728fa3106d730d806436aa4daffected · git
    • 523f1dce37434a9a6623bf46e7893e2b4b10ac3c and later · before 4507a8b9b30344c5ddd8219945f446d47e966a6daffected · git
    • 523f1dce37434a9a6623bf46e7893e2b4b10ac3c and later · before dd0de8cb708951cebf727aa045e8242ba651bb52affected · git
    • 523f1dce37434a9a6623bf46e7893e2b4b10ac3c and later · before a3f9314752dbb6f6aa1f0f2b4c58243bda800738affected · git
    • 523f1dce37434a9a6623bf46e7893e2b4b10ac3c and later · before b04dcbb7f7b1908806b7dc22671cdbe78ff2b82caffected · git

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.123-16.1.123-1
Debian:13linuxbefore 6.12.3-16.12.3-1

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-53238Dec 27, 2024 · Bluetooth: btmtk: adjust the position to init iso data anchor
    22Monitor
  • ← EarlierCVE-2024-53239Dec 27, 2024 · ALSA: 6fire: Release resources at card release
    31Monitor
  • Later →CVE-2024-56532Dec 27, 2024 · ALSA: us122l: Use snd_card_free_when_closed() at disconnection
    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 Linux237f3faf0177bdde728fa3106d730d806436aa4dVendor (CNA)
Linux Linux3993edf44d3df7b6e8c753eac6ac8783473fcbabVendor (CNA)
Linux Linux4507a8b9b30344c5ddd8219945f446d47e966a6dVendor (CNA)
Linux Linux4dd821dcbfcecf7af6a08370b0b217cde2818acfVendor (CNA)
Linux Linuxa3f9314752dbb6f6aa1f0f2b4c58243bda800738Vendor (CNA)
Linux Linuxb04dcbb7f7b1908806b7dc22671cdbe78ff2b82cVendor (CNA)
Linux Linuxcadf1d8e9ddcd74584ec961aeac14ac549b261d8Vendor (CNA)
Linux Linuxdd0de8cb708951cebf727aa045e8242ba651bb52Vendor (CNA)
Linux Linuxebad462eec93b0f701dfe4de98990e7355283801Vendor (CNA)
debian:linux6.1.123-1 · Debian:12Package registry (OSV)

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.

No nightly-computed relations.

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
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-667 · Improper Locking

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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.

Change log

  1. Fix✗ → ✓

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

References

Show all references (10 more)

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

All records