CVE-2024-47748· NVD / CVE Program· CNA Linux

vhost_vdpa: assign irq bypass producer token correctly

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 02e9e9366fefe461719da5d173385b6685f70319, 0c170b1e918b9afac25e2bbd01eaa2bfc0ece8c0, 7cf2fb51175cafe01df8c43fa15a06194a59c6e2; Azure Linux 3.0 ARM 6.6.56.1-5; Azure Linux 3.0 x64 6.6.56.1-5.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 02e9e9366fefe461719da5d173385b6685f70319, 0c170b1e918b9afac25e2bbd01eaa2bfc0ece8c0, 7cf2fb51175cafe01df8c43fa15a06194a59c6e2; Azure Linux 3.0 ARM 6.6.56.1-5; Azure Linux 3.0 x64 6.6.56.1-5 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: vhost_vdpa: assign irq bypass producer token correctly We used to call irq_bypass_unregister_producer() in vhost_vdpa_setup_vq_irq() which is problematic as we don't know if the token pointer is still valid or not. Actually, we use the eventfd_ctx as the token so the life cycle of the token should be bound to the VHOST_SET_VRING_CALL instead of vhost_vdpa_setup_vq_irq() which could be called by set_status(). Fixing this by setting up irq bypass producer's token when handling VHOST_SET_VRING_CALL and un-registering the producer before calling vhost_vring_ioctl() to prevent a possible use after free as eventfd could have been released in vhost_vring_ioctl(). And such registering and unregistering will only be done if DRIVER_OK is set.

HighCVSS 7.8 · v3.1—No exploit Fix available

Memory safety

BDU:2025-03110

Published: Oct 21, 2024
Updated: Aug 5, 2026
EPSS: 0.2% · 11th percentile
CWE: CWE-416

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 31 / 40 · 7.8 / 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: 7.8
CNA · Linux: 7.8; agree

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.

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.

Vendor	Product	CPE
linux	linux kernel	cpe:2.3:o:linux:linux_kernel

Affected versions

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

linux linux kernel5.9 and later · before 5.10.227
linux linux kernel5.11 and later · before 5.15.168
linux linux kernel5.16 and later · before 6.1.113
linux linux kernel6.2 and later · before 6.6.54
linux linux kernel6.7 and later · before 6.10.13
linux linux kernel6.11 and later · before 6.11.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
- 5.9affected
- 2cf1ba9a4d15cb78b96ea97f727b93382c3f9a60 and later · before 0c170b1e918b9afac25e2bbd01eaa2bfc0ece8c0affected · git
- 2cf1ba9a4d15cb78b96ea97f727b93382c3f9a60 and later · before 927a2580208e0f9b0b47b08f1c802b7233a7ba3caffected · git
- 2cf1ba9a4d15cb78b96ea97f727b93382c3f9a60 and later · before ec5f1b54ceb23475049ada6e7a43452cf4df88d1affected · git
- 2cf1ba9a4d15cb78b96ea97f727b93382c3f9a60 and later · before ca64edd7ae93402af2596a952e0d94d545e2b9c0affected · git
- 2cf1ba9a4d15cb78b96ea97f727b93382c3f9a60 and later · before fae9b1776f53aab93ab345bdbf653b991aed717daffected · git
- 2cf1ba9a4d15cb78b96ea97f727b93382c3f9a60 and later · before 7cf2fb51175cafe01df8c43fa15a06194a59c6e2affected · git
- 2cf1ba9a4d15cb78b96ea97f727b93382c3f9a60 and later · before 02e9e9366fefe461719da5d173385b6685f70319affected · git
- before 5.9not affected · semver
- 5.10.227 and later · up to and including 5.10.*not affected · semver

Package-level exposure

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

Ecosystem	Package	Affected range	Fix
Debian:12	linux	before 6.1.115-1	6.1.115-1
Debian:13	linux	before 6.11.2-1	6.11.2-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

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
CVE-2016-5195Race condition in mm/gup.c in the Linux kernel 2.x through 4.x before 4.8.3 allows local users to gain privileges by leveraging incorrect haKEV
83Now

Published before and after this one in the same product

← EarlierCVE-2024-47745Oct 21, 2024 · mm: call the security_mmap_file() LSM hook in remap_file_pages()
31Monitor
← EarlierCVE-2024-47746Oct 21, 2024 · fuse: use exclusive lock when FUSE_I_CACHE_IO_MODE is set
22Monitor
Later →CVE-2024-47749Oct 21, 2024 · RDMA/cxgb4: Added NULL check for lookup_atid
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 / package	Fixed version	Source
Linux Linux	02e9e9366fefe461719da5d173385b6685f70319	Vendor (CNA)
Linux Linux	0c170b1e918b9afac25e2bbd01eaa2bfc0ece8c0	Vendor (CNA)
Linux Linux	7cf2fb51175cafe01df8c43fa15a06194a59c6e2	Vendor (CNA)
Linux Linux	927a2580208e0f9b0b47b08f1c802b7233a7ba3c	Vendor (CNA)
Linux Linux	ca64edd7ae93402af2596a952e0d94d545e2b9c0	Vendor (CNA)
Linux Linux	ec5f1b54ceb23475049ada6e7a43452cf4df88d1	Vendor (CNA)
Linux Linux	fae9b1776f53aab93ab345bdbf653b991aed717d	Vendor (CNA)
Azure Linux 3.0 ARM	6.6.56.1-5 · kernel	Microsoft (MSRC)
Azure Linux 3.0 x64	6.6.56.1-5 · kernel	Microsoft (MSRC)
CBL Mariner 2.0 ARM	5.15.173.1-1 · kernel	Microsoft (MSRC)
CBL Mariner 2.0 x64	5.15.173.1-1 · kernel	Microsoft (MSRC)
debian:linux	6.1.115-1 · Debian:12	Package 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.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

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).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

TR-24-1743 · Oct 22, 2024(Linux Kernel Güvenlik Bildirimi)

All national notices →

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-416 · Use After Free

CVSS vector

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

nvd-primary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

The bug in code

The whole CWE-416 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1free(dev->buf);
2/* ... another thread is still running ... */
3process(dev->buf);

Fixed

1lock(&dev->lock);
2free(dev->buf);
3dev->buf = NULL;
4unlock(&dev->lock);

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

Fix✗ → ✓Sep 28, 2026, 10:11 PM UTC

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

References

git.kernel.org/stable/c/02e9e9366fefe461719da5d173385b6685f70319

Show all references (8 more)

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

All records