drm/i915: Make intel_get_crtc_new_encoder() less oopsy
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.14% (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 0fe6ef82e4f4764e8f556632e4cd93d78d448e99, 54202488c835dab8c648acd107f0bb8eaa699894, 631420b06597a33c72b6dcef78d1c2dea17f452d.
Low priority for now. Upgrade to Linux Linux 0fe6ef82e4f4764e8f556632e4cd93d78d448e99, 54202488c835dab8c648acd107f0bb8eaa699894, 631420b06597a33c72b6dcef78d1c2dea17f452d 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: drm/i915: Make intel_get_crtc_new_encoder() less oopsy The point of the WARN was to print something, not oops straight up. Currently that is precisely what happens if we can't find the connector for the crtc in the atomic state. Get the dev pointer from the atomic state instead of the potentially NULL encoder to avoid that. (cherry picked from commit 3b6692357f70498f617ea1b31a0378070a0acf1c)
- Published
- Oct 4, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 3th percentile
- CWE
- —
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 kernel5.7 and later · before 5.10.180
- linux linux kernel5.11 and later · before 5.15.111
- linux linux kernel5.16 and later · before 6.1.28
- linux linux kernel6.2 and later · before 6.2.15
- linux linux kernel6.3 and later · before 6.3.2
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.7affected
- 3a47ae201e074945bbde0b088e4c1215c07f4d75 and later · before 780f303233c35eeb5132e3ee1cbc8f4cebe86dd2affected · git
- 3a47ae201e074945bbde0b088e4c1215c07f4d75 and later · before 54202488c835dab8c648acd107f0bb8eaa699894affected · git
- 3a47ae201e074945bbde0b088e4c1215c07f4d75 and later · before 0fe6ef82e4f4764e8f556632e4cd93d78d448e99affected · git
- 3a47ae201e074945bbde0b088e4c1215c07f4d75 and later · before 8cd725315c559a8a4d18ac1d7fce1d6b9a667529affected · git
- 3a47ae201e074945bbde0b088e4c1215c07f4d75 and later · before fd8b0abecdf66379e9d25d7448b942b5be379cb2affected · git
- 3a47ae201e074945bbde0b088e4c1215c07f4d75 and later · before 631420b06597a33c72b6dcef78d1c2dea17f452daffected · git
- before 5.7not affected · semver
- 5.10.180 and later · up to and including 5.10.*not affected · semver
- 5.15.111 and later · up to and including 5.15.*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.37-1 | 6.1.37-1 |
| Debian:13 | linux | before 6.3.7-1 | 6.3.7-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-2023-53569Oct 4, 2025 · ext2: Check block size validity during mount31Monitor
- ← EarlierCVE-2023-53570Oct 4, 2025 · wifi: nl80211: fix integer overflow in nl80211_parse_mbssid_elems()31Monitor
- Later →CVE-2023-53572Oct 4, 2025 · clk: imx: scu: use _safe list iterator to avoid a use after free31Monitor
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 | 0fe6ef82e4f4764e8f556632e4cd93d78d448e99 | Vendor (CNA) |
| Linux Linux | 54202488c835dab8c648acd107f0bb8eaa699894 | Vendor (CNA) |
| Linux Linux | 631420b06597a33c72b6dcef78d1c2dea17f452d | Vendor (CNA) |
| Linux Linux | 780f303233c35eeb5132e3ee1cbc8f4cebe86dd2 | Vendor (CNA) |
| Linux Linux | 8cd725315c559a8a4d18ac1d7fce1d6b9a667529 | Vendor (CNA) |
| Linux Linux | fd8b0abecdf66379e9d25d7448b942b5be379cb2 | Vendor (CNA) |
| debian:linux | 6.1.37-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.
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
- 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)
—
CVSS 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 (5 more)Show less
- git.kernel.org/stable/c/54202488c835dab8c648acd107f0bb8eaa699894
- git.kernel.org/stable/c/631420b06597a33c72b6dcef78d1c2dea17f452d
- git.kernel.org/stable/c/780f303233c35eeb5132e3ee1cbc8f4cebe86dd2
- git.kernel.org/stable/c/8cd725315c559a8a4d18ac1d7fce1d6b9a667529
- git.kernel.org/stable/c/fd8b0abecdf66379e9d25d7448b942b5be379cb2
Vendor advisories and official records. Exploit/PoC links are deliberately left out.