vhost/vsock: always initialize seqpacket_allow
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 1e1fdcbdde3b7663e5d8faeb2245b9b151417d22, 3062cb100787a9ddf45de30004b962035cd497fb, 30bd4593669443ac58515e23557dc8cef70d8582.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 1e1fdcbdde3b7663e5d8faeb2245b9b151417d22, 3062cb100787a9ddf45de30004b962035cd497fb, 30bd4593669443ac58515e23557dc8cef70d8582 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/vsock: always initialize seqpacket_allow There are two issues around seqpacket_allow: 1. seqpacket_allow is not initialized when socket is created. Thus if features are never set, it will be read uninitialized. 2. if VIRTIO_VSOCK_F_SEQPACKET is set and then cleared, then seqpacket_allow will not be cleared appropriately (existing apps I know about don't usually do this but it's legal and there's no way to be sure no one relies on this). To fix: - initialize seqpacket_allow after allocation - set it unconditionally in set_features
- Published
- Aug 20, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 11th percentile
- CWE
- CWE-909
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.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
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 kernel5.14 and later · before 5.15.165
- linux linux kernel5.16 and later · before 6.1.103
- linux linux kernel6.2 and later · before 6.6.44
- linux linux kernel6.7 and later · before 6.10.3
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.14affected
- ced7b713711fdd8f99d8d04dc53451441d194c60 and later · before ea558f10fb05a6503c6e655a1b7d81fdf8e5924caffected · git
- ced7b713711fdd8f99d8d04dc53451441d194c60 and later · before 3062cb100787a9ddf45de30004b962035cd497fbaffected · git
- ced7b713711fdd8f99d8d04dc53451441d194c60 and later · before 30bd4593669443ac58515e23557dc8cef70d8582affected · git
- ced7b713711fdd8f99d8d04dc53451441d194c60 and later · before eab96e8716cbfc2834b54f71cc9501ad4eec963baffected · git
- ced7b713711fdd8f99d8d04dc53451441d194c60 and later · before 1e1fdcbdde3b7663e5d8faeb2245b9b151417d22affected · git
- before 5.14not affected · semver
- 5.15.165 and later · up to and including 5.15.*not affected · semver
- 6.1.103 and later · up to and including 6.1.*not affected · semver
- 6.6.44 and later · up to and including 6.6.*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.106-1 | 6.1.106-1 |
| Debian:13 | linux | before 6.10.3-1 | 6.10.3-1 |
Same product
linux: all recordsOther 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 KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
- 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 haKEV83Now
Published before and after this one in the same product
- ← EarlierCVE-2024-43870Aug 20, 2024 · perf: Fix event leak upon exit22Monitor
- ← EarlierCVE-2024-43872Aug 20, 2024 · RDMA/hns: Fix soft lockup under heavy CEQE load22Monitor
- Later →CVE-2024-43874Aug 20, 2024 · crypto: ccp - Fix null pointer dereference in __sev_snp_shutdown_locked22Monitor
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 | 1e1fdcbdde3b7663e5d8faeb2245b9b151417d22 | Vendor (CNA) |
| Linux Linux | 3062cb100787a9ddf45de30004b962035cd497fb | Vendor (CNA) |
| Linux Linux | 30bd4593669443ac58515e23557dc8cef70d8582 | Vendor (CNA) |
| Linux Linux | ea558f10fb05a6503c6e655a1b7d81fdf8e5924c | Vendor (CNA) |
| Linux Linux | eab96e8716cbfc2834b54f71cc9501ad4eec963b | Vendor (CNA) |
| debian:linux | 6.1.106-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.
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 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.
- CVE-2022-49865254 days apartipv6: addrlabel: fix infoleak when sending struct ifaddrlblmsg to network28Monitor
- CVE-2022-50169302 days apartwifi: wil6210: debugfs: fix info leak in wil_write_file_wmi()28Monitor
- CVE-2024-5007669 days apartvt: prevent kernel-infoleak in con_font_get()26Monitor
- CVE-2024-56676130 days apartthermal: testing: Initialize some variables annoteded with _free()22Monitor
- CVE-2024-26635155 days apartllc: Drop support for ETH_P_TR_802_2.22Monitor
- CVE-2022-49217190 days apartscsi: pm8001: Fix abort all task initialization22Monitor
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-1309 · Aug 21, 2024(Linux Kernel Güvenlik Bildirimi)
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-909 · Missing Initialization of ResourceCVSS 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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/3062cb100787a9ddf45de30004b962035cd497fb
- git.kernel.org/stable/c/30bd4593669443ac58515e23557dc8cef70d8582
- git.kernel.org/stable/c/ea558f10fb05a6503c6e655a1b7d81fdf8e5924c
- git.kernel.org/stable/c/eab96e8716cbfc2834b54f71cc9501ad4eec963b
- lists.debian.org/debian-lts-announce/2025/01/msg00001.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.