CVE-2026-63843: drm/amdgpu/jpeg: set no_user_fence for JPEG v4.0.5 ring
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.17% (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 424510b60d4698a75a6ff71acdd88b528f0f39af, b65b7f3f3c18f797f81a2af7c97e2079900ad6db, f26e3f7186cd6ecc93e6af102744d64c798dea7e.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 424510b60d4698a75a6ff71acdd88b528f0f39af, b65b7f3f3c18f797f81a2af7c97e2079900ad6db, f26e3f7186cd6ecc93e6af102744d64c798dea7e 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/amdgpu/jpeg: set no_user_fence for JPEG v4.0.5 ring JPEG rings do not support 64-bit user fence writes, reject CS submissions with user fences. (cherry picked from commit f05d0a4f21fc720116d6e238f23308b199891058)
- Published
- Jul 19, 2026
- Updated
- Oct 22, 2026
- EPSS
- 0.1% · 7th percentile
- CWE
- CWE-754
Report tools
Action score
31
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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.7affected
- 8f98a715da8e906cff5c635f9eb5399b84751557 and later · before 424510b60d4698a75a6ff71acdd88b528f0f39afaffected · git
- 8f98a715da8e906cff5c635f9eb5399b84751557 and later · before f26e3f7186cd6ecc93e6af102744d64c798dea7eaffected · git
- 8f98a715da8e906cff5c635f9eb5399b84751557 and later · before f9bc5633b761cff200c428f61ed0df6212b1c721affected · git
- 8f98a715da8e906cff5c635f9eb5399b84751557 and later · before b65b7f3f3c18f797f81a2af7c97e2079900ad6dbaffected · git
- before 6.7not affected · semver
- 6.12.91 and later · up to and including 6.12.*not affected · semver
- 6.18.33 and later · up to and including 6.18.*not affected · semver
- 7.0.10 and later · up to and including 7.0.*not affected · semver
- 7.1 and laternot affected · original_commit_for_fix
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 kernel6.7 and later · before 6.12.91
- linux linux kernel6.13 and later · before 6.18.33
- linux linux kernel6.19 and later · before 7.0.10
- linux linux kernel7.1
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.12.94-1 | 6.12.94-1 |
| Debian:14 | linux | before 7.0.10-1 | 7.0.10-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-2026-63841Jul 19, 2026 · drm/amdgpu/jpeg: set no_user_fence for JPEG v5.0.1 ring31Monitor
- ← EarlierCVE-2026-63842Jul 19, 2026 · drm/amdgpu/jpeg: set no_user_fence for JPEG v5.0.0 ring31Monitor
- Later →CVE-2026-63844Jul 19, 2026 · drm/amdgpu/jpeg: set no_user_fence for JPEG v4.0.3 ring31Monitor
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 | 424510b60d4698a75a6ff71acdd88b528f0f39af | Vendor (CNA) |
| Linux Linux | b65b7f3f3c18f797f81a2af7c97e2079900ad6db | Vendor (CNA) |
| Linux Linux | f26e3f7186cd6ecc93e6af102744d64c798dea7e | Vendor (CNA) |
| Linux Linux | f9bc5633b761cff200c428f61ed0df6212b1c721 | Vendor (CNA) |
| debian:linux | 6.12.94-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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2025-39682317 days aparttls: fix handling of zero-length records on the rx_listKEV70This week
- CVE-2026-3163786 days apartrxrpc: reject undecryptable rxkad response tickets39Monitor
- CVE-2026-638410 days apartdrm/amdgpu/jpeg: set no_user_fence for JPEG v5.0.1 ring31Monitor
- CVE-2026-638420 days apartdrm/amdgpu/jpeg: set no_user_fence for JPEG v5.0.0 ring31Monitor
- CVE-2026-638440 days apartdrm/amdgpu/jpeg: set no_user_fence for JPEG v4.0.3 ring31Monitor
- CVE-2026-638470 days apartdrm/amdgpu/jpeg: set no_user_fence for JPEG v2.5 ring31Monitor
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0576 · Jul 20, 2026(Linux Kernel Güvenlik Bildirimi)
Not on record for this CVE: 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
- 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-754 · Improper Check for Unusual or Exceptional ConditionsCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
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 (2)
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.