CVE-2024-56725: octeontx2-pf: handle otx2_mbox_get_rsp errors in otx2_dcbnl.c
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.20% (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 54e8b501b3ea9371e4a9aa639c75b681fa5680f0, 69297b0d3369488af259e3a7cf53d69157938ea1, 6ee6cf42dc5230425cfce1ffefa5a8d8a99e6fce; 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 54e8b501b3ea9371e4a9aa639c75b681fa5680f0, 69297b0d3369488af259e3a7cf53d69157938ea1, 6ee6cf42dc5230425cfce1ffefa5a8d8a99e6fce; 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: octeontx2-pf: handle otx2_mbox_get_rsp errors in otx2_dcbnl.c Add error pointer check after calling otx2_mbox_get_rsp().
- Published
- Dec 29, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 10th percentile
- CWE
- CWE-754
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
- 5.18affected
- 8e67558177f8f55dcffa47273c2af0a6f2ab9418 and later · before b94052830e3cd3be7141789a5ce6e62cf9f620a4affected · git
- 8e67558177f8f55dcffa47273c2af0a6f2ab9418 and later · before b99db02209ca4c2e2f53b82049ea3cbc82b54895affected · git
- 8e67558177f8f55dcffa47273c2af0a6f2ab9418 and later · before 54e8b501b3ea9371e4a9aa639c75b681fa5680f0affected · git
- 8e67558177f8f55dcffa47273c2af0a6f2ab9418 and later · before 6ee6cf42dc5230425cfce1ffefa5a8d8a99e6fceaffected · git
- 8e67558177f8f55dcffa47273c2af0a6f2ab9418 and later · before 69297b0d3369488af259e3a7cf53d69157938ea1affected · git
- before 5.18not affected · semver
- 6.1.120 and later · up to and including 6.1.*not affected · semver
- 6.6.64 and later · up to and including 6.6.*not affected · semver
- 6.11.11 and later · up to and including 6.11.*not affected · semver
Affected versions · NVD (4)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel5.18 and later · before 6.1.120
- linux linux kernel6.2 and later · before 6.6.64
- linux linux kernel6.7 and later · before 6.11.11
- linux linux kernel6.12 and later · before 6.12.2
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.123-1 | 6.1.123-1 |
| Debian:13 | linux | before 6.12.3-1 | 6.12.3-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-56723Dec 29, 2024 · mfd: intel_soc_pmic_bxtwc: Use IRQ domain for PMIC devices22Monitor
- ← EarlierCVE-2024-56724Dec 29, 2024 · mfd: intel_soc_pmic_bxtwc: Use IRQ domain for TMU device22Monitor
- Later →CVE-2024-56726Dec 29, 2024 · octeontx2-pf: handle otx2_mbox_get_rsp errors in cn10k.c22Monitor
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 | 54e8b501b3ea9371e4a9aa639c75b681fa5680f0 | Vendor (CNA) |
| Linux Linux | 69297b0d3369488af259e3a7cf53d69157938ea1 | Vendor (CNA) |
| Linux Linux | 6ee6cf42dc5230425cfce1ffefa5a8d8a99e6fce | Vendor (CNA) |
| Linux Linux | b94052830e3cd3be7141789a5ce6e62cf9f620a4 | Vendor (CNA) |
| Linux Linux | b99db02209ca4c2e2f53b82049ea3cbc82b54895 | 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) |
| debian:linux | 6.1.123-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.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2025-39682250 days aparttls: fix handling of zero-length records on the rx_listKEV70This week
- CVE-2026-31637481 days apartrxrpc: reject undecryptable rxkad response tickets39Monitor
- CVE-2024-4772769 days apartx86/tdx: Fix "in-kernel MMIO" check31Monitor
- CVE-2024-42284134 days aparttipc: Return non-zero value from tipc_udp_addr2str() on error31Monitor
- CVE-2024-42159152 days apartscsi: mpi3mr: Sanitise num_phys31Monitor
- CVE-2024-42160152 days apartf2fs: check validation of fault attrs in f2fs_build_fault_attr()31Monitor
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-754 · Improper Check for Unusual or Exceptional ConditionsCVSS 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 (5 more)Show less
- git.kernel.org/stable/c/69297b0d3369488af259e3a7cf53d69157938ea1
- git.kernel.org/stable/c/6ee6cf42dc5230425cfce1ffefa5a8d8a99e6fce
- git.kernel.org/stable/c/b94052830e3cd3be7141789a5ce6e62cf9f620a4
- git.kernel.org/stable/c/b99db02209ca4c2e2f53b82049ea3cbc82b54895
- lists.debian.org/debian-lts-announce/2025/03/msg00001.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.