Full vulnerability report · 2025

CVE-2023-54098High confidence

drm/i915/gvt: fix gvt debugfs destroy

Linux · Linux

7.3HighCVSS 3.1

Recommended action

Within 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available

Distribution package intelligence

Ubuntu vendor package status

Canonical’s release and source-package findings are shown separately from local repository availability.

9 package states

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Ubuntu release	Source package	Vendor state	Fixed version	Evidence
Ubuntu 24.04 LTSnoble · standard archive	`linux-azure-6.11`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-gcp-6.11`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-hwe-6.11`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-lowlatency-hwe-6.11`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-nvidia-6.11`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-oem-6.11`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-raspi-realtime`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-realtime`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-riscv`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 11 Sept 2026

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current

ENISA EUVD identifier

EUVD-2023-60347

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state: Present in the current official mapping
Known exploitation: Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score: Not supplied in the stored EUVD record
Advisory evidence: No linked advisory details stored yet

Recommended actionWithin 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available

What, why and how

In the Linux kernel, the following vulnerability has been resolved: drm/i915/gvt: fix gvt debugfs destroy When gvt debug fs is destroyed, need to have a sane check if drm minor's debugfs root is still available or not, otherwise in case like device remove through unbinding, drm minor's debugfs directory has already been removed, then intel_gvt_debugfs_clean() would act upon dangling pointer like below oops. i915 0000:00:02.0: Direct firmware load for i915/gvt/vid_0x8086_did_0x1926_rid_0x0a.golden_hw_state failed with error -2 i915 0000:00:02.0: MDEV: Registered Console: switching to colour dummy device 80x25 i915 0000:00:02.0: MDEV: Unregistering BUG: kernel NULL pointer dereference, address: 00000000000000a0 PGD 0 P4D 0 Oops: 0002 [#1] PREEMPT SMP PTI CPU: 2 PID: 2486 Comm: gfx-unbind.sh Tainted: G I 6.1.0-rc8+ #15 Hardware name: Dell Inc. XPS 13 9350/0JXC1H, BIOS 1.13.0 02/10/2020 RIP: 0010:down_write+0x1f/0x90 Code: 1d ff ff 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 53 48 89 fb e8 62 c0 ff ff bf 01 00 00 00 e8 28 5e 31 ff 31 c0 ba 01 00 00 00 <f0> 48 0f b1 13 75 33 65 48 8b 04 25 c0 bd 01 00 48 89 43 08 bf 01 RSP: 0018:ffff9eb3036ffcc8 EFLAGS: 00010246 RAX: 0000000000000000 RBX: 00000000000000a0 RCX: ffffff8100000000 RDX: 0000000000000001 RSI: 0000000000000064 RDI: ffffffffa48787a8 RBP: ffff9eb3036ffd30 R08: ffffeb1fc45a0608 R09: ffffeb1fc45a05c0 R10: 0000000000000002 R11: 0000000000000000 R12: 0000000000000000 R13: ffff91acc33fa328 R14: ffff91acc033f080 R15: ffff91acced533e0 FS: 00007f6947bba740(0000) GS:ffff91ae36d00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00000000000000a0 CR3: 00000001133a2002 CR4: 00000000003706e0 Call Trace: <TASK> simple_recursive_removal+0x9f/0x2a0 ? start_creating.part.0+0x120/0x120 ? _raw_spin_lock+0x13/0x40 debugfs_remove+0x40/0x60 intel_gvt_debugfs_clean+0x15/0x30 [kvmgt] intel_gvt_clean_device+0x49/0xe0 [kvmgt] intel_gvt_driver_remove+0x2f/0xb0 i915_driver_remove+0xa4/0xf0 i915_pci_remove+0x1a/0x30 pci_device_remove+0x33/0xa0 device_release_driver_internal+0x1b2/0x230 unbind_store+0xe0/0x110 kernfs_fop_write_iter+0x11b/0x1f0 vfs_write+0x203/0x3d0 ksys_write+0x63/0xe0 do_syscall_64+0x37/0x90 entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP: 0033:0x7f6947cb5190 Code: 40 00 48 8b 15 71 9c 0d 00 f7 d8 64 89 02 48 c7 c0 ff ff ff ff eb b7 0f 1f 00 80 3d 51 24 0e 00 00 74 17 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 58 c3 0f 1f 80 00 00 00 00 48 83 ec 28 48 89 RSP: 002b:00007ffcbac45a28 EFLAGS: 00000202 ORIG_RAX: 0000000000000001 RAX: ffffffffffffffda RBX: 000000000000000d RCX: 00007f6947cb5190 RDX: 000000000000000d RSI: 0000555e35c866a0 RDI: 0000000000000001 RBP: 0000555e35c866a0 R08: 0000000000000002 R09: 0000555e358cb97c R10: 0000000000000000 R11: 0000000000000202 R12: 0000000000000001 R13: 000000000000000d R14: 0000000000000000 R15: 0000555e358cb8e0 </TASK> Modules linked in: kvmgt CR2: 00000000000000a0 ---[ end trace 0000000000000000 ]---

What

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation

Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.

No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material

Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.

None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path: local access → vulnerable operation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface: Local
Privileges required: Low: a basic authenticated account is required
User interaction: Required interaction required
Attack complexity: Low: no specialised conditions are recorded
Security boundary: Unchanged: impact remains within the vulnerable component's security authority
Weakness ? CWE means Common Weakness Enumeration.: CWE not yet assigned
CVSS vector ? CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.: CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UIRequiredUser interaction: Another user must perform an action for exploitation to succeed.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land: The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2023-60347Official EUVD mapping

0 linked advisory records.

Official EUVD record

BSI · German · WID-SEC-2025-2929Linux Kernel: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einer Denial-of-Service- Bedingung führen oder eine Speicherbeschädigung verursachen können.

Official advisory

CERT-FR · French · CERTFR-2026-AVI-0225Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2023-54089 Référence CVE CVE-2023-54090 https://www.cve.org/CVERecord?id=CVE-2023-54090 Référence CVE CVE-2023-54091 https://www.cve.org/CVERecord?id=CVE-2023-54091 Référence CVE CVE-2023-54092 https://www.cve.org/CVERecord?id=CVE-2023-54092 Référence CVE CVE-2023-54093 https://www.cve.org/CVERecord?id=CVE-2023-54093 Référence CVE CVE-2023-54094 https://www.cve.org/CVERecord?id=CVE-2023-54094 Référence CVE CVE-2023-54095 https://www.cve.org/CVERecord?id=CVE-2023-54095 Référence CVE CVE-2023-54096 https://www.cve.org/CVERecord?id=CVE-2023-54096 Référence CVE CVE-2023-54097 https://www.cve.org/CVERecord?id=CVE-2023-54097 Référence CVE CVE-2023-54098 https://www.cve.org/CVERecord?id=CVE-2023-54098 Référence CVE CVE-2023-54099 https://www.cve.org/CVERecord?id=CVE-2023-54099 Référence CVE CVE-2023-54100 https://www.cve.org/CVERecord?id=CVE-2023-54100 Référence CVE CVE-2023-54101 https://www.cve.org/CVERecord?id=CVE-2023-54101 Référence CVE CVE-2023-54102 https://www.cve.org/CVERecord?id=CVE-2023-54102 Référence CVE CVE-2023-54104 https://www.cve.org/CVERecord?id=CVE-2023-54104 Référence CVE CVE-2023-54106 https://www.cve.org/CVERecord?id=CVE-2023-54106 Référence CVE CVE-2023-54108 https://www.cve.org/CVERecord?id=CVE-2023-54108 Référence CVE CVE-2023-54110 https://www.cve.org/CVERecord?id=

Official advisory

CERT-FR · French · CERTFR-2026-AVI-0170Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2023-54079 Référence CVE CVE-2023-54083 https://www.cve.org/CVERecord?id=CVE-2023-54083 Référence CVE CVE-2023-54084 https://www.cve.org/CVERecord?id=CVE-2023-54084 Référence CVE CVE-2023-54090 https://www.cve.org/CVERecord?id=CVE-2023-54090 Référence CVE CVE-2023-54091 https://www.cve.org/CVERecord?id=CVE-2023-54091 Référence CVE CVE-2023-54092 https://www.cve.org/CVERecord?id=CVE-2023-54092 Référence CVE CVE-2023-54095 https://www.cve.org/CVERecord?id=CVE-2023-54095 Référence CVE CVE-2023-54096 https://www.cve.org/CVERecord?id=CVE-2023-54096 Référence CVE CVE-2023-54097 https://www.cve.org/CVERecord?id=CVE-2023-54097 Référence CVE CVE-2023-54098 https://www.cve.org/CVERecord?id=CVE-2023-54098 Référence CVE CVE-2023-54100 https://www.cve.org/CVERecord?id=CVE-2023-54100 Référence CVE CVE-2023-54102 https://www.cve.org/CVERecord?id=CVE-2023-54102 Référence CVE CVE-2023-54104 https://www.cve.org/CVERecord?id=CVE-2023-54104 Référence CVE CVE-2023-54108 https://www.cve.org/CVERecord?id=CVE-2023-54108 Référence CVE CVE-2023-54110 https://www.cve.org/CVERecord?id=CVE-2023-54110 Référence CVE CVE-2023-54111 https://www.cve.org/CVERecord?id=CVE-2023-54111 Référence CVE CVE-2023-54112 https://www.cve.org/CVERecord?id=CVE-2023-54112 Référence CVE CVE-2023-54115 https://www.cve.org/CVERecord?id=

Official advisory

CERT-FR · French · CERTFR-2026-AVI-0108Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2023-54089 Référence CVE CVE-2023-54090 https://www.cve.org/CVERecord?id=CVE-2023-54090 Référence CVE CVE-2023-54091 https://www.cve.org/CVERecord?id=CVE-2023-54091 Référence CVE CVE-2023-54092 https://www.cve.org/CVERecord?id=CVE-2023-54092 Référence CVE CVE-2023-54093 https://www.cve.org/CVERecord?id=CVE-2023-54093 Référence CVE CVE-2023-54094 https://www.cve.org/CVERecord?id=CVE-2023-54094 Référence CVE CVE-2023-54095 https://www.cve.org/CVERecord?id=CVE-2023-54095 Référence CVE CVE-2023-54096 https://www.cve.org/CVERecord?id=CVE-2023-54096 Référence CVE CVE-2023-54097 https://www.cve.org/CVERecord?id=CVE-2023-54097 Référence CVE CVE-2023-54098 https://www.cve.org/CVERecord?id=CVE-2023-54098 Référence CVE CVE-2023-54099 https://www.cve.org/CVERecord?id=CVE-2023-54099 Référence CVE CVE-2023-54100 https://www.cve.org/CVERecord?id=CVE-2023-54100 Référence CVE CVE-2023-54101 https://www.cve.org/CVERecord?id=CVE-2023-54101 Référence CVE CVE-2023-54102 https://www.cve.org/CVERecord?id=CVE-2023-54102 Référence CVE CVE-2023-54104 https://www.cve.org/CVERecord?id=CVE-2023-54104 Référence CVE CVE-2023-54106 https://www.cve.org/CVERecord?id=CVE-2023-54106 Référence CVE CVE-2023-54107 https://www.cve.org/CVERecord?id=CVE-2023-54107 Référence CVE CVE-2023-54108 https://www.cve.org/CVERecord?id=

Official advisory

Patch and workaround

Operational remediation based on structured source evidence.

Status ? Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.: Patch available
Affected: Linux: bc7b0be316aebac42eb9e8e54c984609555944da < bb7c7b2c89d2feb347b6f9bffc1c75987adb1048, bc7b0be316aebac42eb9e8e54c984609555944da < ae9a61511736cc71a99f01e8b7b90f6fb6128ed8, bc7b0be316aebac42eb9e8e54c984609555944da < b85c8536fda3d1ed07c6d87a661ffe18d6eb214b, bc7b0be316aebac42eb9e8e54c984609555944da < fe340500baf84b6531c9fc508b167525b9bf6446, bc7b0be316aebac42eb9e8e54c984609555944da < c4b850d1f448a901fbf4f7f36dec38c84009b489, 4.16
Fixed: Linux: < 4.16, 5.10.163 ≤ 5.10.*, 5.15.87 ≤ 5.15.*, 6.0.19 ≤ 6.0.*, 6.1.5 ≤ 6.1.*, 6.2 ≤ *
Action: Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
Workaround: No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.

Evidence and provenance

Published 24 Dec 2025 · Last source change 5 Aug 2026, 09:17 UTC · CWE not yet assigned

CVE recordCVE.org · 5.2

CVSS sourceCNA

EPSS source

The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.

FIRST · tracked since 2026-08-14

European sourceENISA EUVD · EUVD-2023-60347

Product sourceCNA

Remediation sourceCVE/CNA references

CWE sourceUnavailable

NVD statusNVD not scheduled

Missing structured fields: CWE classification. Missing data is not evidence of low risk; review the primary advisory.

Material change intelligence

What changed after publication

View recent updates →

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

2025-12-24CVE published

2026-08-05Fixed release or patch reference recorded

ENISA EUVD · EUVD-2023-60347↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗

Technical terms and abbreviations used in this report

CVE: Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS: Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS: Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE: Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA: CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP: Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD: National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT: A computer security incident response team that publishes warnings or coordinates incident response.
PoC: Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF: Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL: Living off the land: abuse of legitimate tools or system functions during an attack.

drm/i915/gvt: fix gvt debugfs destroy

National CERT insights ?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

EUVD-2023-60347

What, why and how

Exploit reality and attack path

Official authority intelligence

Patch and workaround

Evidence and provenance

National CERT insights
?
CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.