ice: ptp: don't WARN when controlling PF is unavailable
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.16% (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 6.13, bb3f21edc7056cdf44a7f7bd7ba65af40741838c, c73f365707d3b1b78b7d16e1f029020d1ae50d0f.
Low priority for now. Upgrade to Linux Linux 6.13, bb3f21edc7056cdf44a7f7bd7ba65af40741838c, c73f365707d3b1b78b7d16e1f029020d1ae50d0f 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: ice: ptp: don't WARN when controlling PF is unavailable In VFIO passthrough setups, it is possible to pass through only a PF which doesn't own the source timer. In that case the PTP controlling PF (adapter->ctrl_pf) is never initialized in the VM, so ice_get_ctrl_ptp() returns NULL and triggers WARN_ON() in ice_ptp_setup_pf(). Since this is an expected behavior in that configuration, replace WARN_ON() with an informational message and return -EOPNOTSUPP.
- Published
- May 8, 2026
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 4th percentile
- CWE
- CWE-617
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
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 kernel6.12.11 and later · before 6.13
- linux linux kernel6.13 and later · before 6.18.24
- linux linux kernel6.19 and later · before 6.19.14
- linux linux kernel7.0
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
- 2f59743be4d9568cad2d9cf697d1b897975421ed, 6.13affected
- e800654e85b5b27966fc6493201f5f8cf658beb6 and later · before e19675b384e9dcaca1bd5e4a67b8ad136eccfbe8affected · git
- e800654e85b5b27966fc6493201f5f8cf658beb6 and later · before c73f365707d3b1b78b7d16e1f029020d1ae50d0faffected · git
- e800654e85b5b27966fc6493201f5f8cf658beb6 and later · before bb3f21edc7056cdf44a7f7bd7ba65af40741838caffected · git
- 6.12.11 and later · before 6.13affected · semver
- before 6.13not affected · semver
- 6.18.24 and later · up to and including 6.18.*not affected · semver
- 6.19.14 and later · up to and including 6.19.*not affected · semver
- 7.0 and laternot affected · original_commit_for_fix
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 | from 0 | — |
| Debian:14 | linux | before 6.19.14-1 | 6.19.14-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-2026-43344May 8, 2026 · perf/x86/intel/uncore: Fix die ID init and look up bugs22Monitor
- ← EarlierCVE-2026-43345May 8, 2026 · net: ipa: fix event ring index not programmed for IPA v5.0+30Monitor
- Later →CVE-2026-43347May 8, 2026 · arm64: dts: qcom: monaco: Reserve full Gunyah metadata region30Monitor
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 | 6.13 | Vendor (CNA) |
| Linux Linux | bb3f21edc7056cdf44a7f7bd7ba65af40741838c | Vendor (CNA) |
| Linux Linux | c73f365707d3b1b78b7d16e1f029020d1ae50d0f | Vendor (CNA) |
| Linux Linux | e19675b384e9dcaca1bd5e4a67b8ad136eccfbe8 | Vendor (CNA) |
| debian:linux | 6.19.14-1 · Debian:14 | 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-2026-317397 days apartcrypto: tegra - Add missing CRYPTO_ALG_ASYNC35Monitor
- CVE-2026-5295247 days apartiommu: Fix WARN_ON in __iommu_group_set_domain_nofail() due to reset35Monitor
- CVE-2026-4611720 days apartRDMA/mana: Remove user triggerable WARN_ON() in mana_ib_create_qp_rss()31Monitor
- CVE-2026-3139835 days apartmm/rmap: fix incorrect pte restoration for lazyfree folios31Monitor
- CVE-2025-39803235 days apartscsi: ufs: core: Remove WARN_ON_ONCE() call from ufshcd_uic_cmd_compl()31Monitor
- CVE-2026-4602719 days apartnet/smc: avoid early lgr access in smc_clc_wait_msg30Monitor
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
- 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-617 · Reachable AssertionCVSS 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
- 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.