CVE-2024-50264: vsock/virtio: Initialization of the dangling pointer occurring in vsk->trans
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.35% (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 2a6a4e69f255b7aed17f93995691ab4f0d3c2203, 44d29897eafd0e1196453d3003a4d5e0b968eeab, 5f092a4271f6dccf88fe0d132475a17b69ef71df; azl3 kernel 6.6.57.1-7 on Azure Linux 3.0 6.6.64.2-1; azl3 kernel 6.6.64.2-1 on Azure Linux 3.0 6.6.64.2-1.
Low priority for now. Upgrade to Linux Linux 2a6a4e69f255b7aed17f93995691ab4f0d3c2203, 44d29897eafd0e1196453d3003a4d5e0b968eeab, 5f092a4271f6dccf88fe0d132475a17b69ef71df; azl3 kernel 6.6.57.1-7 on Azure Linux 3.0 6.6.64.2-1; azl3 kernel 6.6.64.2-1 on Azure Linux 3.0 6.6.64.2-1 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: vsock/virtio: Initialization of the dangling pointer occurring in vsk->trans During loopback communication, a dangling pointer can be created in vsk->trans, potentially leading to a Use-After-Free condition. This issue is resolved by initializing vsk->trans to NULL.
- BDU:2024-11660
- ALSA-2024:10943
- ALSA-2024:10944
- ALSA-2025:2627
- RHSA-2024:10943
- RHSA-2024:10944
- RHSA-2025:2627
- RHSA-2025:3510
- RLSA-2024:10943
- RLSA-2024:10944
- SUSE-SU-2024:4313-1
- SUSE-SU-2024:4317-1
- SUSE-SU-2024:4345-1
- SUSE-SU-2024:4346-1
- SUSE-SU-2024:4388-1
- SUSE-SU-2025:0083-1
- SUSE-SU-2025:0084-1
- SUSE-SU-2025:0085-1
- SUSE-SU-2025:0089-1
- SUSE-SU-2025:0090-1
- Published
- Nov 18, 2024
- Updated
- Aug 5, 2026
- EPSS
- 0.3% · 28th percentile
- CWE
- CWE-416
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
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
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 helpAffected 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 kernel4.8 and later · before 4.19.324
- linux linux kernel4.20 and later · before 5.4.286
- linux linux kernel5.5 and later · before 5.10.230
- linux linux kernel5.11 and later · before 5.15.172
- linux linux kernel5.16 and later · before 6.1.117
- linux linux kernel6.2 and later · before 6.6.61
- linux linux kernel6.7 and later · before 6.11.8
- linux linux kernel6.12
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
- 4.8affected
- 06a8fc78367d070720af960dcecec917d3ae5f3b and later · before 5f092a4271f6dccf88fe0d132475a17b69ef71dfaffected · git
- 06a8fc78367d070720af960dcecec917d3ae5f3b and later · before fd8ae346692a56b4437d626c5460c7104980f389affected · git
- 06a8fc78367d070720af960dcecec917d3ae5f3b and later · before eb1bdcb7dfc30b24495ee4c5533af0ed135cb5f1affected · git
- 06a8fc78367d070720af960dcecec917d3ae5f3b and later · before 2a6a4e69f255b7aed17f93995691ab4f0d3c2203affected · git
- 06a8fc78367d070720af960dcecec917d3ae5f3b and later · before 44d29897eafd0e1196453d3003a4d5e0b968eeabaffected · git
- 06a8fc78367d070720af960dcecec917d3ae5f3b and later · before b110196fec44fe966952004bd426967c2a8fd358affected · git
- 06a8fc78367d070720af960dcecec917d3ae5f3b and later · before 5f970935d09934222fdef3d0e20c648ea7a963c1affected · git
- 06a8fc78367d070720af960dcecec917d3ae5f3b and later · before 6ca575374dd9a507cdd16dfa0e78c2e9e20bd05faffected · git
- before 4.8not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:8 | bpftool | before 4.18.0-553.32.1.el8_10 | 4.18.0-553.32.1.el8_10 |
| AlmaLinux:8 | kernel | before 4.18.0-553.32.1.el8_10 | 4.18.0-553.32.1.el8_10 |
| AlmaLinux:8 | kernel-abi-stablelists | before 4.18.0-553.32.1.el8_10 | 4.18.0-553.32.1.el8_10 |
| AlmaLinux:8 | kernel-core | before 4.18.0-553.32.1.el8_10 | 4.18.0-553.32.1.el8_10 |
| AlmaLinux:8 | kernel-cross-headers | before 4.18.0-553.32.1.el8_10 | 4.18.0-553.32.1.el8_10 |
| AlmaLinux:8 | kernel-debug | before 4.18.0-553.32.1.el8_10 | 4.18.0-553.32.1.el8_10 |
| AlmaLinux:8 | kernel-debug-core | before 4.18.0-553.32.1.el8_10 | 4.18.0-553.32.1.el8_10 |
| AlmaLinux:8 | kernel-debug-devel | before 4.18.0-553.32.1.el8_10 | 4.18.0-553.32.1.el8_10 |
| AlmaLinux:8 | kernel-debug-modules | before 4.18.0-553.32.1.el8_10 | 4.18.0-553.32.1.el8_10 |
| AlmaLinux:8 | kernel-debug-modules-extra | before 4.18.0-553.32.1.el8_10 | 4.18.0-553.32.1.el8_10 |
| AlmaLinux:8 | kernel-devel | before 4.18.0-553.32.1.el8_10 | 4.18.0-553.32.1.el8_10 |
| AlmaLinux:8 | kernel-doc | before 4.18.0-553.32.1.el8_10 | 4.18.0-553.32.1.el8_10 |
| AlmaLinux:8 | kernel-headers | before 4.18.0-553.32.1.el8_10 | 4.18.0-553.32.1.el8_10 |
| AlmaLinux:8 | kernel-modules | before 4.18.0-553.32.1.el8_10 | 4.18.0-553.32.1.el8_10 |
| AlmaLinux:8 | kernel-modules-extra | before 4.18.0-553.32.1.el8_10 | 4.18.0-553.32.1.el8_10 |
| AlmaLinux:8 | kernel-rt | before 4.18.0-553.32.1.rt7.373.el8_10 | 4.18.0-553.32.1.rt7.373.el8_10 |
| AlmaLinux:8 | kernel-rt-core | before 4.18.0-553.32.1.rt7.373.el8_10 | 4.18.0-553.32.1.rt7.373.el8_10 |
| AlmaLinux:8 | kernel-rt-debug | before 4.18.0-553.32.1.rt7.373.el8_10 | 4.18.0-553.32.1.rt7.373.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-core | before 4.18.0-553.32.1.rt7.373.el8_10 | 4.18.0-553.32.1.rt7.373.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-devel | before 4.18.0-553.32.1.rt7.373.el8_10 | 4.18.0-553.32.1.rt7.373.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-modules | before 4.18.0-553.32.1.rt7.373.el8_10 | 4.18.0-553.32.1.rt7.373.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-modules-extra | before 4.18.0-553.32.1.rt7.373.el8_10 | 4.18.0-553.32.1.rt7.373.el8_10 |
| AlmaLinux:8 | kernel-rt-devel | before 4.18.0-553.32.1.rt7.373.el8_10 | 4.18.0-553.32.1.rt7.373.el8_10 |
| AlmaLinux:8 | kernel-rt-modules | before 4.18.0-553.32.1.rt7.373.el8_10 | 4.18.0-553.32.1.rt7.373.el8_10 |
+96
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- 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 KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2023-39176Nov 18, 2024 · Kernel: ksmbd: transform header out-of-bounds read information disclosure vulnerability30Monitor
- ← EarlierCVE-2023-52921Nov 18, 2024 · drm/amdgpu: fix possible UAF in amdgpu_cs_pass1()31Monitor
- Later →CVE-2024-50265Nov 18, 2024 · ocfs2: remove entry once instead of null-ptr-dereference in ocfs2_xa_remove()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 | 2a6a4e69f255b7aed17f93995691ab4f0d3c2203 | Vendor (CNA) |
| Linux Linux | 44d29897eafd0e1196453d3003a4d5e0b968eeab | Vendor (CNA) |
| Linux Linux | 5f092a4271f6dccf88fe0d132475a17b69ef71df | Vendor (CNA) |
| Linux Linux | 5f970935d09934222fdef3d0e20c648ea7a963c1 | Vendor (CNA) |
| Linux Linux | 6ca575374dd9a507cdd16dfa0e78c2e9e20bd05f | Vendor (CNA) |
| Linux Linux | b110196fec44fe966952004bd426967c2a8fd358 | Vendor (CNA) |
| Linux Linux | eb1bdcb7dfc30b24495ee4c5533af0ed135cb5f1 | Vendor (CNA) |
| Linux Linux | fd8ae346692a56b4437d626c5460c7104980f389 | Vendor (CNA) |
| azl3 kernel 6.6.57.1-7 on Azure Linux 3.0 | 6.6.64.2-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 kernel 6.6.64.2-1 on Azure Linux 3.0 | 6.6.64.2-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 kernel 5.15.167.1-2 on CBL Mariner 2.0 | 5.15.173.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 kernel 5.15.167.1-2 on CBL-Mariner 2.0 | 5.15.173.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 kernel 5.15.173.1-1 on CBL Mariner 2.0 | 5.15.173.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| almalinux:bpftool | 4.18.0-553.32.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel | 4.18.0-553.32.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-abi-stablelists | 4.18.0-553.32.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-core | 4.18.0-553.32.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-cross-headers | 4.18.0-553.32.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug | 4.18.0-553.32.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug-core | 4.18.0-553.32.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug-devel | 4.18.0-553.32.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug-modules | 4.18.0-553.32.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug-modules-extra | 4.18.0-553.32.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-devel | 4.18.0-553.32.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-doc | 4.18.0-553.32.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| debian:linux | 6.1.119-1 · Debian:12 | Package registry (OSV) |
| red hat:bpftool | 0:4.18.0-553.32.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:bpftool-debuginfo | 0:4.18.0-553.32.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel | 0:4.18.0-553.32.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel-abi-stablelists | 0:4.18.0-553.32.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
+22
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 researchersFinders, 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
- 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 FreeCVSS 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 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
free(dev->buf);
/* ... another thread is still running ... */
process(dev->buf);Fixed
lock(&dev->lock);
free(dev->buf);
dev->buf = NULL;
unlock(&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✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (10 more)Show less
- git.kernel.org/stable/c/2a6a4e69f255b7aed17f93995691ab4f0d3c2203
- git.kernel.org/stable/c/44d29897eafd0e1196453d3003a4d5e0b968eeab
- git.kernel.org/stable/c/5f092a4271f6dccf88fe0d132475a17b69ef71df
- git.kernel.org/stable/c/5f970935d09934222fdef3d0e20c648ea7a963c1
- git.kernel.org/stable/c/6ca575374dd9a507cdd16dfa0e78c2e9e20bd05f
- git.kernel.org/stable/c/b110196fec44fe966952004bd426967c2a8fd358
- git.kernel.org/stable/c/eb1bdcb7dfc30b24495ee4c5533af0ed135cb5f1
- git.kernel.org/stable/c/fd8ae346692a56b4437d626c5460c7104980f389
- lists.debian.org/debian-lts-announce/2025/01/msg00001.html
- lists.debian.org/debian-lts-announce/2025/03/msg00002.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.