CVE-2024-49855: nbd: fix race between timeout and normal completion
In the Linux kernel, the following vulnerability has been resolved:
nbd: fix race between timeout and normal completion
If request timetout is handled by nbd_requeue_cmd(), normal completion
has to be stopped for avoiding to complete this requeued request, other
use-after-free can be triggered.
Fix the race by clearing NBD_CMD_INFLIGHT in nbd_requeue_cmd(), meantime
make sure that cmd->lock is grabbed for clearing the flag and the
requeue.
Security readout for executives and security teams
Plain-English summary
A timing flaw in the Linux Network Block Device subsystem can let a timed-out request also complete normally. This double handling may access freed memory, potentially crashing the kernel or corrupting data. The supplied record rates it critical, but does not establish a practical attack path.
Executive priority
Treat as urgent for infrastructure that uses NBD, particularly availability-sensitive or multi-tenant systems. Validate exposure before assuming the 9.8 network rating represents direct internet risk. Patch confirmed affected systems through supported distribution channels and track completion through the required kernel activation or reboot.
Technical view
A race exists between nbd_requeue_cmd() and normal request completion. When a timeout requeues a request without stopping its normal completion path, the request can be completed after requeueing and trigger a use-after-free. The stable fix clears NBD_CMD_INFLIGHT while holding cmd->lock during flag clearing and requeueing.
Likely exposure
Exposure is most likely on systems running an affected Linux kernel and actively using the Network Block Device subsystem. The supplied version data identifies several affected kernel lines but is complex and includes commit identifiers; confirm applicability against each distribution's kernel package and vendor advisory.
Exploitation context
The supplied record is not in CISA KEV and provides no evidence of active exploitation or a public exploit. Its CVSS 3.1 score is 9.8, but the sources do not demonstrate the required access path or practical confidentiality, integrity, and availability impact. Absence from KEV does not prove exploitation is absent.
Researcher notes
The security consequence described by the kernel source is a race-triggered use-after-free. The bundle does not provide reproduction details, exploitability evidence, affected configurations, or proof of remote reachability. Researchers should distinguish upstream kernel versions from distribution backports and verify whether NBD is configured and exercised before rating environmental risk.
Mitigation direction
Install a vendor-supported kernel package containing the applicable stable fix.
Prioritize systems actively using Linux Network Block Device functionality.
Review Linux distribution advisories to identify fixed package versions.
Follow vendor guidance for activating the updated kernel, including any required reboot.
Validation and detection
Inventory kernel versions and identify hosts using the Network Block Device subsystem.
Compare each kernel package against its distribution's affected and fixed version guidance.
Confirm the running kernel after remediation matches the installed fixed package.
Review relevant kernel and service logs for timeout, requeue, crash, or memory-corruption symptoms.
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-49855 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.