CVE-2024-42113: net: txgbe: initialize num_q_vectors for MSI/INTx interrupts
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.23% (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 7c36711a2cd8059c2d24f5e5c1d76e8ea2d5613c, 9edc7a83cd40ac96ff14fe3a17a38f7ace6611df, c98969226d1fe0c1dd779db8b1c444bc5294fc83.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 7c36711a2cd8059c2d24f5e5c1d76e8ea2d5613c, 9edc7a83cd40ac96ff14fe3a17a38f7ace6611df, c98969226d1fe0c1dd779db8b1c444bc5294fc83 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: net: txgbe: initialize num_q_vectors for MSI/INTx interrupts When using MSI/INTx interrupts, wx->num_q_vectors is uninitialized. Thus there will be kernel panic in wx_alloc_q_vectors() to allocate queue vectors.
- Published
- Jul 30, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 15th percentile
- CWE
- CWE-908
Report tools
Action score
22
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.
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.
Is your version affected? Check itNoroxi 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 |
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
- 6.3affected
- 3f703186113fac0f3c965204b2cbb22a03322e2c and later · before 9edc7a83cd40ac96ff14fe3a17a38f7ace6611dfaffected · git
- 3f703186113fac0f3c965204b2cbb22a03322e2c and later · before c98969226d1fe0c1dd779db8b1c444bc5294fc83affected · git
- 3f703186113fac0f3c965204b2cbb22a03322e2c and later · before 7c36711a2cd8059c2d24f5e5c1d76e8ea2d5613caffected · git
- before 6.3not affected · semver
- 6.6.39 and later · up to and including 6.6.*not affected · semver
- 6.9.9 and later · up to and including 6.9.*not affected · semver
- 6.10 and laternot affected · original_commit_for_fix
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel6.3 and later · before 6.6.39
- linux linux kernel6.7 and later · before 6.9.9
- linux linux kernel6.10
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:13 | linux | before 6.9.9-1 | 6.9.9-1 |
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-2024-42111Jul 30, 2024 · btrfs: always do the basic checks for btrfs_qgroup_inherit structure25Monitor
- ← EarlierCVE-2024-42112Jul 30, 2024 · net: txgbe: free isb resources at the right time31Monitor
- Later →CVE-2024-42115Jul 30, 2024 · jffs2: Fix potential illegal address access in jffs2_free_inode22Monitor
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 | 7c36711a2cd8059c2d24f5e5c1d76e8ea2d5613c | Vendor (CNA) |
| Linux Linux | 9edc7a83cd40ac96ff14fe3a17a38f7ace6611df | Vendor (CNA) |
| Linux Linux | c98969226d1fe0c1dd779db8b1c444bc5294fc83 | Vendor (CNA) |
| debian:linux | 6.9.9-1 · Debian:13 | 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.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2024-50302112 days apartHID: core: zero-initialize the report bufferKEV52Plan
- CVE-2024-4768583 days apartnetfilter: nf_reject_ipv6: fix nf_reject_ip6_tcphdr_put()36Monitor
- CVE-2024-3689861 days apartgpiolib: cdev: fix uninitialised kfifo31Monitor
- CVE-2021-4755367 days apartsched/scs: Reset task stack state in bringup_cpu()31Monitor
- CVE-2024-2702290 days apartfork: defer linking file vma until vma is fully initialized31Monitor
- CVE-2024-50143100 days apartudf: fix uninit-value use in udf_get_fileshortad31Monitor
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-24-1106 · Jul 31, 2024(Linux Kernel Güncellemesi)
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.
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-908 · Use of Uninitialized ResourceCVSS 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.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.