BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2024
CVE-2023-52528High confidence

net: usb: smsc75xx: Fix uninit-value access in __smsc75xx_read_reg

Linux · Linux

5.5MediumCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 1 structured product or package state remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:Low, lowered one band.downgradedsince 11 May 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.23% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: No default targetRemediation target: Normal maintenance

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 1 structured product or package state remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

5 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 1 affected package state shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

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.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.5.8-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.64-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.5.8-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.5.8-1Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, 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 feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2023-52528 · CSAF 2.0 · revision 71 · interimSUSE Product Security TeamCVE-2023-52528
229 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • kernel-default as component of SUSE Enterprise Storage 7.1
  • kernel-default-devel as component of SUSE Enterprise Storage 7.1
  • kernel-devel as component of SUSE Enterprise Storage 7.1
  • kernel-macros as component of SUSE Enterprise Storage 7.1
  • kernel-source as component of SUSE Enterprise Storage 7.1
  • reiserfs-kmp-default as component of SUSE Enterprise Storage 7.1
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 12 SP2
Summary
In the Linux kernel, the following vulnerability has been resolved: net: usb: smsc75xx: Fix uninit-value access in __smsc75xx_read_reg syzbot reported the following uninit-value access issue: ===================================================== BUG: KMSAN: uninit-value in smsc75xx_wait_ready drivers/net/usb/smsc75xx.c:975 [inline] BUG: KMSAN: uninit-value in smsc75xx_bind+0x5c9/0x11e0 drivers/net/usb/smsc75xx.c:1482 CPU: 0 PID: 8696 Comm: kworker/0:3 Not tainted 5.8.0-rc5-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Workqueue: usb_hub_wq hub_event Call Trace: __dump_stack lib/dump_stack.c:77 [inline] dump_stack+0x21c/0x280 lib/dump_stack.c:118 kmsan_report+0xf7/0x1e0 mm/kmsan/kmsan_report.c:121 __msan_warning+0x58/0xa0 mm/kmsan/kmsan_instr.c:215 smsc75xx_wait_ready drivers/net/usb/smsc75xx.c:975 [inline] smsc75xx_bind+0x5c9/0x11e0 drivers/net/usb/smsc75xx.c:1482 usbnet_probe+0x1152/0x3f90 drivers/net/usb/usbnet.c:1737 usb_probe_interface+0xece/0x1550 drivers/usb/core/driver.c:374 really_probe+0xf20/0x20b0 drivers/base/dd.c:529 driver_probe_device+0x293/0x390 drivers/base/dd.c:701 __device_attach_driver+0x63f/0x830 drivers/base/dd.c:807 bus_for_each_drv+0x2ca/0x3f0 drivers/base/bus.c:431 __device_attach+0x4e2/0x7f0 drivers/base/dd.c:873 device_initial_probe+0x4a/0x60 drivers/base/dd.c:920 bus_probe_device+0x177/0x3d0 drivers/base/bus.c:491 device_add+0x3b0e/0x40d0 drivers/base/core.c:2680 usb_set_configuration+0x380f/0x3f10 drivers/usb/core/message.c:2032 usb_generic_driver_probe+0x138/0x300 drivers/usb/core/generic.c:241 usb_probe_device+0x311/0x490 drivers/usb/core/driver.c:272 really_probe+0xf20/0x20b0 drivers/base/dd.c:529 driver_probe_device+0x293/0x390 drivers/base/dd.c:701 __device_attach_driver+0x63f/0x830 drivers/base/dd.c:807 bus_for_each_drv+0x2ca/0x3f0 drivers/base/bus.c:431 __device_attach+0x4e2/0x7f0 drivers/base/dd.c:873 device_initial_probe+0x4a/0x60 drivers/base/dd.c:920 bus_probe_device+0x177/0x3d0 drivers/base/bus.c:491 device_add+0x3b0e/0x40d0 drivers/base/core.c:2680 usb_new_device+0x1bd4/0x2a30 drivers/usb/core/hub.c:2554 hub_port_connect drivers/usb/core/hub.c:5208 [inline] hub_port_connect_change drivers/usb/core/hub.c:5348 [inline] port_event drivers/usb/core/hub.c:5494 [inline] hub_event+0x5e7b/0x8a70 drivers/usb/core/hub.c:5576 process_one_work+0x1688/0x2140 kernel/workqueue.c:2269 worker_thread+0x10bc/0x2730 kernel/workqueue.c:2415 kthread+0x551/0x590 kernel/kthread.c:292 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:293 Local variable ----buf.i87@smsc75xx_bind created at: __smsc75xx_read_reg drivers/net/usb/smsc75xx.c:83 [inline] smsc75xx_wait_ready drivers/net/usb/smsc75xx.c:968 [inline] smsc75xx_bind+0x485/0x11e0 drivers/net/usb/smsc75xx.c:1482 __smsc75xx_read_reg drivers/net/usb/smsc75xx.c:83 [inline] smsc75xx_wait_ready drivers/net/usb/smsc75xx.c:968 [inline] smsc75xx_bind+0x485/0x11e0 drivers/net/usb/smsc75xx.c:1482 This issue is caused because usbnet_read_cmd() reads less bytes than requested (zero byte in the reproducer). In this case, 'buf' is not properly filled. This patch fixes the issue by returning -ENODATA if usbnet_read_cmd() reads less bytes than requested.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
Optional official sources

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

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

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-57153

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 actionPatch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 1 structured product or package state remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: net: usb: smsc75xx: Fix uninit-value access in __smsc75xx_read_reg syzbot reported the following uninit-value access issue: ===================================================== BUG: KMSAN: uninit-value in smsc75xx_wait_ready drivers/net/usb/smsc75xx.c:975 [inline] BUG: KMSAN: uninit-value in smsc75xx_bind+0x5c9/0x11e0 drivers/net/usb/smsc75xx.c:1482 CPU: 0 PID: 8696 Comm: kworker/0:3 Not tainted 5.8.0-rc5-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Workqueue: usb_hub_wq hub_event Call Trace: __dump_stack lib/dump_stack.c:77 [inline] dump_stack+0x21c/0x280 lib/dump_stack.c:118 kmsan_report+0xf7/0x1e0 mm/kmsan/kmsan_report.c:121 __msan_warning+0x58/0xa0 mm/kmsan/kmsan_instr.c:215 smsc75xx_wait_ready drivers/net/usb/smsc75xx.c:975 [inline] smsc75xx_bind+0x5c9/0x11e0 drivers/net/usb/smsc75xx.c:1482 usbnet_probe+0x1152/0x3f90 drivers/net/usb/usbnet.c:1737 usb_probe_interface+0xece/0x1550 drivers/usb/core/driver.c:374 really_probe+0xf20/0x20b0 drivers/base/dd.c:529 driver_probe_device+0x293/0x390 drivers/base/dd.c:701 __device_attach_driver+0x63f/0x830 drivers/base/dd.c:807 bus_for_each_drv+0x2ca/0x3f0 drivers/base/bus.c:431 __device_attach+0x4e2/0x7f0 drivers/base/dd.c:873 device_initial_probe+0x4a/0x60 drivers/base/dd.c:920 bus_probe_device+0x177/0x3d0 drivers/base/bus.c:491 device_add+0x3b0e/0x40d0 drivers/base/core.c:2680 usb_set_configuration+0x380f/0x3f10 drivers/usb/core/message.c:2032 usb_generic_driver_probe+0x138/0x300 drivers/usb/core/generic.c:241 usb_probe_device+0x311/0x490 drivers/usb/core/driver.c:272 really_probe+0xf20/0x20b0 drivers/base/dd.c:529 driver_probe_device+0x293/0x390 drivers/base/dd.c:701 __device_attach_driver+0x63f/0x830 drivers/base/dd.c:807 bus_for_each_drv+0x2ca/0x3f0 drivers/base/bus.c:431 __device_attach+0x4e2/0x7f0 drivers/base/dd.c:873 device_initial_probe+0x4a/0x60 drivers/base/dd.c:920 bus_probe_device+0x177/0x3d0 drivers/base/bus.c:491 device_add+0x3b0e/0x40d0 drivers/base/core.c:2680 usb_new_device+0x1bd4/0x2a30 drivers/usb/core/hub.c:2554 hub_port_connect drivers/usb/core/hub.c:5208 [inline] hub_port_connect_change drivers/usb/core/hub.c:5348 [inline] port_event drivers/usb/core/hub.c:5494 [inline] hub_event+0x5e7b/0x8a70 drivers/usb/core/hub.c:5576 process_one_work+0x1688/0x2140 kernel/workqueue.c:2269 worker_thread+0x10bc/0x2730 kernel/workqueue.c:2415 kthread+0x551/0x590 kernel/kthread.c:292 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:293 Local variable ----buf.i87@smsc75xx_bind created at: __smsc75xx_read_reg drivers/net/usb/smsc75xx.c:83 [inline] smsc75xx_wait_ready drivers/net/usb/smsc75xx.c:968 [inline] smsc75xx_bind+0x485/0x11e0 drivers/net/usb/smsc75xx.c:1482 __smsc75xx_read_reg drivers/net/usb/smsc75xx.c:83 [inline] smsc75xx_wait_ready drivers/net/usb/smsc75xx.c:968 [inline] smsc75xx_bind+0x485/0x11e0 drivers/net/usb/smsc75xx.c:1482 This issue is caused because usbnet_read_cmd() reads less bytes than requested (zero byte in the reproducer). In this case, 'buf' is not properly filled. This patch fixes the issue by returning -ENODATA if usbnet_read_cmd() reads less bytes than requested.

What

In the Linux kernel, the following vulnerability has been resolved: net: usb: smsc75xx: Fix uninit-value access in __smsc75xx_read_reg syzbot reported the following uninit-value access issue: ===================================================== BUG: KMSAN: uninit-value in smsc75xx_wait_ready drivers/net/usb/smsc75xx.c:975 [inline] BUG: KMSAN: uninit-value in smsc75xx_bind+0x5c9/0x11e0 drivers/net/usb/smsc75xx.c:1482 CPU: 0 PID: 8696 Comm: kworker/0:3 Not tainted 5.8.0-rc5-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Workqueue: usb_hub_wq hub_event Call Trace: __dump_stack lib/dump_stack.c:77 [inline] dump_stack+0x21c/0x280 lib/dump_stack.c:118 kmsan_report+0xf7/0x1e0 mm/kmsan/kmsan_report.c:121 __msan_warning+0x58/0xa0 mm/kmsan/kmsan_instr.c:215 smsc75xx_wait_ready drivers/net/usb/smsc75xx.c:975 [inline] smsc75xx_bind+0x5c9/0x11e0 drivers/net/usb/smsc75xx.c:1482 usbnet_probe+0x1152/0x3f90 drivers/net/usb/usbnet.c:1737 usb_probe_interface+0xece/0x1550 drivers/usb/core/driver.c:374 really_probe+0xf20/0x20b0 drivers/base/dd.c:529 driver_probe_device+0x293/0x390 drivers/base/dd.c:701 __device_attach_driver+0x63f/0x830 drivers/base/dd.c:807 bus_for_each_drv+0x2ca/0x3f0 drivers/base/bus.c:431 __device_attach+0x4e2/0x7f0 drivers/base/dd.c:873 device_initial_probe+0x4a/0x60 drivers/base/dd.c:920 bus_probe_device+0x177/0x3d0 drivers/base/bus.c:491 device_add+0x3b0e/0x40d0 drivers/base/core.c:2680 usb_set_configuration+0x380f/0x3f10 drivers/usb/core/message.c:2032 usb_generic_driver_probe+0x138/0x300 drivers/usb/core/generic.c:241 usb_probe_device+0x311/0x490 drivers/usb/core/driver.c:272 really_probe+0xf20/0x20b0 drivers/base/dd.c:529 driver_probe_device+0x293/0x390 drivers/base/dd.c:701 __device_attach_driver+0x63f/0x830 drivers/base/dd.c:807 bus_for_each_drv+0x2ca/0x3f0 drivers/base/bus.c:431 __device_attach+0x4e2/0x7f0 drivers/base/dd.c:873 device_initial_probe+0x4a/0x60 drivers/base/dd.c:920 bus_probe_device+0x177/0x3d0 drivers/base/bus.c:491 device_add+0x3b0e/0x40d0 drivers/base/core.c:2680 usb_new_device+0x1bd4/0x2a30 drivers/usb/core/hub.c:2554 hub_port_connect drivers/usb/core/hub.c:5208 [inline] hub_port_connect_change drivers/usb/core/hub.c:5348 [inline] port_event drivers/usb/core/hub.c:5494 [inline] hub_event+0x5e7b/0x8a70 drivers/usb/core/hub.c:5576 process_one_work+0x1688/0x2140 kernel/workqueue.c:2269 worker_thread+0x10bc/0x2730 kernel/workqueue.c:2415 kthread+0x551/0x590 kernel/kthread.c:292 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:293 Local variable ----buf.i87@smsc75xx_bind created at: __smsc75xx_read_reg drivers/net/usb/smsc75xx.c:83 [inline] smsc75xx_wait_ready drivers/net/usb/smsc75xx.c:968 [inline] smsc75xx_bind+0x485/0x11e0 drivers/net/usb/smsc75xx.c:1482 __smsc75xx_read_reg drivers/net/usb/smsc75xx.c:83 [inline] smsc75xx_wait_ready drivers/net/usb/smsc75xx.c:968 [inline] smsc75xx_bind+0x485/0x11e0 drivers/net/usb/smsc75xx.c:1482 This issue is caused because usbnet_read_cmd() reads less bytes than requested (zero byte in the reproducer). In this case, 'buf' is not properly filled. This patch fixes the issue by returning -ENODATA if usbnet_read_cmd() reads less bytes than requested.

Why

The product uses or accesses a resource that has not been initialized.

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

In the Linux kernel, the following vulnerability has been resolved: net: usb: smsc75xx: Fix uninit-value access in __smsc75xx_read_reg syzbot reported the following uninit-value access issue: ===================================================== BUG: KMSAN: uninit-value in smsc75xx_wait_ready drivers/net/usb/smsc75xx.c:975 [inline] BUG: KMSAN: uninit-value in smsc75xx_bind+0x5c9/0x11e0 drivers/net/usb/smsc75xx.c:1482 CPU: 0 PID: 8696 Comm: kworker/0:3 Not tainted 5.8.0-rc5-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Workqueue: usb_hub_wq hub_event Call Trace: __dump_stack lib/dump_stack.c:77 [inline] dump_stack+0x21c/0x280 lib/dump_stack.c:118 kmsan_report+0xf7/0x1e0 mm/kmsan/kmsan_report.c:121 __msan_warning+0x58/0xa0 mm/kmsan/kmsan_instr.c:215 smsc75xx_wait_ready drivers/net/usb/smsc75xx.c:975 [inline] smsc75xx_bind+0x5c9/0x11e0 drivers/net/usb/smsc75xx.c:1482 usbnet_probe+0x1152/0x3f90 drivers/net/usb/usbnet.c:1737 usb_probe_interface+0xece/0x1550 drivers/usb/core/driver.c:374 really_probe+0xf20/0x20b0 drivers/base/dd.c:529 driver_probe_device+0x293/0x390 drivers/base/dd.c:701 __device_attach_driver+0x63f/0x830 drivers/base/dd.c:807 bus_for_each_drv+0x2ca/0x3f0 drivers/base/bus.c:431 __device_attach+0x4e2/0x7f0 drivers/base/dd.c:873 device_initial_probe+0x4a/0x60 drivers/base/dd.c:920 bus_probe_device+0x177/0x3d0 drivers/base/bus.c:491 device_add+0x3b0e/0x40d0 drivers/base/core.c:2680 usb_set_configuration+0x380f/0x3f10 drivers/usb/core/message.c:2032 usb_generic_driver_probe+0x138/0x300 drivers/usb/core/generic.c:241 usb_probe_device+0x311/0x490 drivers/usb/core/driver.c:272 really_probe+0xf20/0x20b0 drivers/base/dd.c:529 driver_probe_device+0x293/0x390 drivers/base/dd.c:701 __device_attach_driver+0x63f/0x830 drivers/base/dd.c:807 bus_for_each_drv+0x2ca/0x3f0 drivers/base/bus.c:431 __device_attach+0x4e2/0x7f0 drivers/base/dd.c:873 device_initial_probe+0x4a/0x60 drivers/base/dd.c:920 bus_probe_device+0x177/0x3d0 drivers/base/bus.c:491 device_add+0x3b0e/0x40d0 drivers/base/core.c:2680 usb_new_device+0x1bd4/0x2a30 drivers/usb/core/hub.c:2554 hub_port_connect drivers/usb/core/hub.c:5208 [inline] hub_port_connect_change drivers/usb/core/hub.c:5348 [inline] port_event drivers/usb/core/hub.c:5494 [inline] hub_event+0x5e7b/0x8a70 drivers/usb/core/hub.c:5576 process_one_work+0x1688/0x2140 kernel/workqueue.c:2269 worker_thread+0x10bc/0x2730 kernel/workqueue.c:2415 kthread+0x551/0x590 kernel/kthread.c:292 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:293 Local variable ----buf.i87@smsc75xx_bind created at: __smsc75xx_read_reg drivers/net/usb/smsc75xx.c:83 [inline] smsc75xx_wait_ready drivers/net/usb/smsc75xx.c:968 [inline] smsc75xx_bind+0x485/0x11e0 drivers/net/usb/smsc75xx.c:1482 __smsc75xx_read_reg drivers/net/usb/smsc75xx.c:83 [inline] smsc75xx_wait_ready drivers/net/usb/smsc75xx.c:968 [inline] smsc75xx_bind+0x485/0x11e0 drivers/net/usb/smsc75xx.c:1482 This issue is caused because usbnet_read_cmd() reads less bytes than requested (zero byte in the reproducer). In this case, 'buf' is not properly filled. This patch fixes the issue by returning -ENODATA if usbnet_read_cmd() reads less bytes than requested.

Why

The product uses or accesses a resource that has not been initialized.

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.

02

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 → Use of Uninitialized Resource → 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
None
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: a standard category for the underlying weakness.
CWE-908 ↗

CWE-908: Use of Uninitialized Resource. The product uses or accesses a resource that has not been initialized.

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:N/S:U/C:N/I:N/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.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.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.
CWE-908
A

Official authority intelligence

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

BSI · German · WID-SEC-2024-0534Linux Kernel: Mehrere Schwachstellen

Ein lokaler Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand herbeizuführen oder einen nicht spezifizierten Angriff durchzuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20240306Security Bulletin 06 Mar 2024

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 06 Mar 2024, published on 6 March 2024. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-1057Multiples vulnérabilités dans les produits VMware

d?id=CVE-2023-52478 Référence CVE CVE-2023-52487 https://www.cve.org/CVERecord?id=CVE-2023-52487 Référence CVE CVE-2023-52490 https://www.cve.org/CVERecord?id=CVE-2023-52490 Référence CVE CVE-2023-52501 https://www.cve.org/CVERecord?id=CVE-2023-52501 Référence CVE CVE-2023-52513 https://www.cve.org/CVERecord?id=CVE-2023-52513 Référence CVE CVE-2023-52516 https://www.cve.org/CVERecord?id=CVE-2023-52516 Référence CVE CVE-2023-52519 https://www.cve.org/CVERecord?id=CVE-2023-52519 Référence CVE CVE-2023-52520 https://www.cve.org/CVERecord?id=CVE-2023-52520 Référence CVE CVE-2023-52523 https://www.cve.org/CVERecord?id=CVE-2023-52523 Référence CVE CVE-2023-52528 https://www.cve.org/CVERecord?id=CVE-2023-52528 Référence CVE CVE-2023-52532 https://www.cve.org/CVERecord?id=CVE-2023-52532 Référence CVE CVE-2023-52560 https://www.cve.org/CVERecord?id=CVE-2023-52560 Référence CVE CVE-2023-52565 https://www.cve.org/CVERecord?id=CVE-2023-52565 Référence CVE CVE-2023-52568 https://www.cve.org/CVERecord?id=CVE-2023-52568 Référence CVE CVE-2023-52570 https://www.cve.org/CVERecord?id=CVE-2023-52570 Référence CVE CVE-2023-52582 https://www.cve.org/CVERecord?id=CVE-2023-52582 Référence CVE CVE-2023-52643 https://www.cve.org/CVERecord?id=CVE-2023-52643 Référence CVE CVE-2023-52646 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0997Multiples vulnérabilités dans le noyau Linux d'Ubuntu

rg/CVERecord?id=CVE-2020-1983 Référence CVE CVE-2020-7039 https://www.cve.org/CVERecord?id=CVE-2020-7039 Référence CVE CVE-2020-8608 https://www.cve.org/CVERecord?id=CVE-2020-8608 Référence CVE CVE-2021-3592 https://www.cve.org/CVERecord?id=CVE-2021-3592 Référence CVE CVE-2021-3594 https://www.cve.org/CVERecord?id=CVE-2021-3594 Référence CVE CVE-2021-47212 https://www.cve.org/CVERecord?id=CVE-2021-47212 Référence CVE CVE-2022-36402 https://www.cve.org/CVERecord?id=CVE-2022-36402 Référence CVE CVE-2022-48666 https://www.cve.org/CVERecord?id=CVE-2022-48666 Référence CVE CVE-2023-3019 https://www.cve.org/CVERecord?id=CVE-2023-3019 Référence CVE CVE-2023-52528 https://www.cve.org/CVERecord?id=CVE-2023-52528 Référence CVE CVE-2023-52531 https://www.cve.org/CVERecord?id=CVE-2023-52531 Référence CVE CVE-2023-52614 https://www.cve.org/CVERecord?id=CVE-2023-52614 Référence CVE CVE-2023-52887 https://www.cve.org/CVERecord?id=CVE-2023-52887 Référence CVE CVE-2023-52888 https://www.cve.org/CVERecord?id=CVE-2023-52888 Référence CVE CVE-2023-52889 https://www.cve.org/CVERecord?id=CVE-2023-52889 Référence CVE CVE-2023-52918 https://www.cve.org/CVERecord?id=CVE-2023-52918 Référence CVE CVE-2024-25741 https://www.cve.org/CVERecord?id=CVE-2024-25741 Référence CVE CVE-2024-25744 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0906Multiples vulnérabilités dans le noyau Linux d'Ubuntu

//ubuntu.com/security/notices/USN-7073-2 Bulletin de sécurité Ubuntu USN-7074-1 du 17 octobre 2024 https://ubuntu.com/security/notices/USN-7074-1 Bulletin de sécurité Ubuntu USN-7076-1 du 17 octobre 2024 https://ubuntu.com/security/notices/USN-7076-1 Référence CVE CVE-2021-47188 https://www.cve.org/CVERecord?id=CVE-2021-47188 Référence CVE CVE-2022-48791 https://www.cve.org/CVERecord?id=CVE-2022-48791 Référence CVE CVE-2022-48863 https://www.cve.org/CVERecord?id=CVE-2022-48863 Référence CVE CVE-2023-52510 https://www.cve.org/CVERecord?id=CVE-2023-52510 Référence CVE CVE-2023-52527 https://www.cve.org/CVERecord?id=CVE-2023-52527 Référence CVE CVE-2023-52528 https://www.cve.org/CVERecord?id=CVE-2023-52528 Référence CVE CVE-2023-52809 https://www.cve.org/CVERecord?id=CVE-2023-52809 Référence CVE CVE-2024-26602 https://www.cve.org/CVERecord?id=CVE-2024-26602 Référence CVE CVE-2024-26641 https://www.cve.org/CVERecord?id=CVE-2024-26641 Référence CVE CVE-2024-26651 https://www.cve.org/CVERecord?id=CVE-2024-26651 Référence CVE CVE-2024-26677 https://www.cve.org/CVERecord?id=CVE-2024-26677 Référence CVE CVE-2024-26733 https://www.cve.org/CVERecord?id=CVE-2024-26733 Référence CVE CVE-2024-26754 https://www.cve.org/CVERecord?id=CVE-2024-26754 Référence CVE CVE-2024-26810 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0741Multiples vulnérabilités dans Juniper Secure Analytics

ord?id=CVE-2023-48795 Référence CVE CVE-2023-5090 https://www.cve.org/CVERecord?id=CVE-2023-5090 Référence CVE CVE-2023-52425 https://www.cve.org/CVERecord?id=CVE-2023-52425 Référence CVE CVE-2023-52439 https://www.cve.org/CVERecord?id=CVE-2023-52439 Référence CVE CVE-2023-52445 https://www.cve.org/CVERecord?id=CVE-2023-52445 Référence CVE CVE-2023-52464 https://www.cve.org/CVERecord?id=CVE-2023-52464 Référence CVE CVE-2023-52477 https://www.cve.org/CVERecord?id=CVE-2023-52477 Référence CVE CVE-2023-52513 https://www.cve.org/CVERecord?id=CVE-2023-52513 Référence CVE CVE-2023-52520 https://www.cve.org/CVERecord?id=CVE-2023-52520 Référence CVE CVE-2023-52528 https://www.cve.org/CVERecord?id=CVE-2023-52528 Référence CVE CVE-2023-52560 https://www.cve.org/CVERecord?id=CVE-2023-52560 Référence CVE CVE-2023-52565 https://www.cve.org/CVERecord?id=CVE-2023-52565 Référence CVE CVE-2023-52578 https://www.cve.org/CVERecord?id=CVE-2023-52578 Référence CVE CVE-2023-52594 https://www.cve.org/CVERecord?id=CVE-2023-52594 Référence CVE CVE-2023-52595 https://www.cve.org/CVERecord?id=CVE-2023-52595 Référence CVE CVE-2023-52598 https://www.cve.org/CVERecord?id=CVE-2023-52598 Référence CVE CVE-2023-52606 https://www.cve.org/CVERecord?id=CVE-2023-52606 Référence CVE CVE-2023-52607 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0646Multiples vulnérabilités dans les produits IBM

d?id=CVE-2023-46604 Référence CVE CVE-2023-48795 https://www.cve.org/CVERecord?id=CVE-2023-48795 Référence CVE CVE-2023-51767 https://www.cve.org/CVERecord?id=CVE-2023-51767 Référence CVE CVE-2023-52425 https://www.cve.org/CVERecord?id=CVE-2023-52425 Référence CVE CVE-2023-52439 https://www.cve.org/CVERecord?id=CVE-2023-52439 Référence CVE CVE-2023-52445 https://www.cve.org/CVERecord?id=CVE-2023-52445 Référence CVE CVE-2023-52477 https://www.cve.org/CVERecord?id=CVE-2023-52477 Référence CVE CVE-2023-52513 https://www.cve.org/CVERecord?id=CVE-2023-52513 Référence CVE CVE-2023-52520 https://www.cve.org/CVERecord?id=CVE-2023-52520 Référence CVE CVE-2023-52528 https://www.cve.org/CVERecord?id=CVE-2023-52528 Référence CVE CVE-2023-52565 https://www.cve.org/CVERecord?id=CVE-2023-52565 Référence CVE CVE-2023-52578 https://www.cve.org/CVERecord?id=CVE-2023-52578 Référence CVE CVE-2023-52594 https://www.cve.org/CVERecord?id=CVE-2023-52594 Référence CVE CVE-2023-52595 https://www.cve.org/CVERecord?id=CVE-2023-52595 Référence CVE CVE-2023-52598 https://www.cve.org/CVERecord?id=CVE-2023-52598 Référence CVE CVE-2023-52606 https://www.cve.org/CVERecord?id=CVE-2023-52606 Référence CVE CVE-2023-52607 https://www.cve.org/CVERecord?id=CVE-2023-52607 Référence CVE CVE-2023-52610 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0471Multiples vulnérabilités dans le noyau Linux de Red Hat

ecord?id=CVE-2022-48627 Référence CVE CVE-2022-48669 https://www.cve.org/CVERecord?id=CVE-2022-48669 Référence CVE CVE-2023-2166 https://www.cve.org/CVERecord?id=CVE-2023-2166 Référence CVE CVE-2023-2176 https://www.cve.org/CVERecord?id=CVE-2023-2176 Référence CVE CVE-2023-52439 https://www.cve.org/CVERecord?id=CVE-2023-52439 Référence CVE CVE-2023-52445 https://www.cve.org/CVERecord?id=CVE-2023-52445 Référence CVE CVE-2023-52477 https://www.cve.org/CVERecord?id=CVE-2023-52477 Référence CVE CVE-2023-52513 https://www.cve.org/CVERecord?id=CVE-2023-52513 Référence CVE CVE-2023-52520 https://www.cve.org/CVERecord?id=CVE-2023-52520 Référence CVE CVE-2023-52528 https://www.cve.org/CVERecord?id=CVE-2023-52528 Référence CVE CVE-2023-52565 https://www.cve.org/CVERecord?id=CVE-2023-52565 Référence CVE CVE-2023-52578 https://www.cve.org/CVERecord?id=CVE-2023-52578 Référence CVE CVE-2023-52594 https://www.cve.org/CVERecord?id=CVE-2023-52594 Référence CVE CVE-2023-52595 https://www.cve.org/CVERecord?id=CVE-2023-52595 Référence CVE CVE-2023-52598 https://www.cve.org/CVERecord?id=CVE-2023-52598 Référence CVE CVE-2023-52606 https://www.cve.org/CVERecord?id=CVE-2023-52606 Référence CVE CVE-2023-52607 https://www.cve.org/CVERecord?id=CVE-2023-52607 Référence CVE CVE-2023-52610 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0458Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2023-52470 Référence CVE CVE-2023-52474 https://www.cve.org/CVERecord?id=CVE-2023-52474 Référence CVE CVE-2023-52476 https://www.cve.org/CVERecord?id=CVE-2023-52476 Référence CVE CVE-2023-52477 https://www.cve.org/CVERecord?id=CVE-2023-52477 Référence CVE CVE-2023-52486 https://www.cve.org/CVERecord?id=CVE-2023-52486 Référence CVE CVE-2023-52488 https://www.cve.org/CVERecord?id=CVE-2023-52488 Référence CVE CVE-2023-52509 https://www.cve.org/CVERecord?id=CVE-2023-52509 Référence CVE CVE-2023-52515 https://www.cve.org/CVERecord?id=CVE-2023-52515 Référence CVE CVE-2023-52524 https://www.cve.org/CVERecord?id=CVE-2023-52524 Référence CVE CVE-2023-52528 https://www.cve.org/CVERecord?id=CVE-2023-52528 Référence CVE CVE-2023-52575 https://www.cve.org/CVERecord?id=CVE-2023-52575 Référence CVE CVE-2023-52583 https://www.cve.org/CVERecord?id=CVE-2023-52583 Référence CVE CVE-2023-52587 https://www.cve.org/CVERecord?id=CVE-2023-52587 Référence CVE CVE-2023-52590 https://www.cve.org/CVERecord?id=CVE-2023-52590 Référence CVE CVE-2023-52591 https://www.cve.org/CVERecord?id=CVE-2023-52591 Référence CVE CVE-2023-52595 https://www.cve.org/CVERecord?id=CVE-2023-52595 Référence CVE CVE-2023-52598 https://www.cve.org/CVERecord?id=CVE-2023-52598 Référence CVE CVE-2023-52607 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0440Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2023-52474 Référence CVE CVE-2023-52476 https://www.cve.org/CVERecord?id=CVE-2023-52476 Référence CVE CVE-2023-52477 https://www.cve.org/CVERecord?id=CVE-2023-52477 Référence CVE CVE-2023-52486 https://www.cve.org/CVERecord?id=CVE-2023-52486 Référence CVE CVE-2023-52488 https://www.cve.org/CVERecord?id=CVE-2023-52488 Référence CVE CVE-2023-52502 https://www.cve.org/CVERecord?id=CVE-2023-52502 Référence CVE CVE-2023-52509 https://www.cve.org/CVERecord?id=CVE-2023-52509 Référence CVE CVE-2023-52515 https://www.cve.org/CVERecord?id=CVE-2023-52515 Référence CVE CVE-2023-52524 https://www.cve.org/CVERecord?id=CVE-2023-52524 Référence CVE CVE-2023-52528 https://www.cve.org/CVERecord?id=CVE-2023-52528 Référence CVE CVE-2023-52575 https://www.cve.org/CVERecord?id=CVE-2023-52575 Référence CVE CVE-2023-52583 https://www.cve.org/CVERecord?id=CVE-2023-52583 Référence CVE CVE-2023-52587 https://www.cve.org/CVERecord?id=CVE-2023-52587 Référence CVE CVE-2023-52590 https://www.cve.org/CVERecord?id=CVE-2023-52590 Référence CVE CVE-2023-52591 https://www.cve.org/CVERecord?id=CVE-2023-52591 Référence CVE CVE-2023-52595 https://www.cve.org/CVERecord?id=CVE-2023-52595 Référence CVE CVE-2023-52598 https://www.cve.org/CVERecord?id=CVE-2023-52598 Référence CVE CVE-2023-52607 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0420Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2023-52476 Référence CVE CVE-2023-52477 https://www.cve.org/CVERecord?id=CVE-2023-52477 Référence CVE CVE-2023-52486 https://www.cve.org/CVERecord?id=CVE-2023-52486 Référence CVE CVE-2023-52488 https://www.cve.org/CVERecord?id=CVE-2023-52488 Référence CVE CVE-2023-52500 https://www.cve.org/CVERecord?id=CVE-2023-52500 Référence CVE CVE-2023-52503 https://www.cve.org/CVERecord?id=CVE-2023-52503 Référence CVE CVE-2023-52509 https://www.cve.org/CVERecord?id=CVE-2023-52509 Référence CVE CVE-2023-52515 https://www.cve.org/CVERecord?id=CVE-2023-52515 Référence CVE CVE-2023-52524 https://www.cve.org/CVERecord?id=CVE-2023-52524 Référence CVE CVE-2023-52528 https://www.cve.org/CVERecord?id=CVE-2023-52528 Référence CVE CVE-2023-52561 https://www.cve.org/CVERecord?id=CVE-2023-52561 Référence CVE CVE-2023-52575 https://www.cve.org/CVERecord?id=CVE-2023-52575 Référence CVE CVE-2023-52583 https://www.cve.org/CVERecord?id=CVE-2023-52583 Référence CVE CVE-2023-52585 https://www.cve.org/CVERecord?id=CVE-2023-52585 Référence CVE CVE-2023-52587 https://www.cve.org/CVERecord?id=CVE-2023-52587 Référence CVE CVE-2023-52589 https://www.cve.org/CVERecord?id=CVE-2023-52589 Référence CVE CVE-2023-52590 https://www.cve.org/CVERecord?id=CVE-2023-52590 Référence CVE CVE-2023-52591 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0363Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2023-52513 Référence CVE CVE-2023-52515 https://www.cve.org/CVERecord?id=CVE-2023-52515 Référence CVE CVE-2023-52517 https://www.cve.org/CVERecord?id=CVE-2023-52517 Référence CVE CVE-2023-52518 https://www.cve.org/CVERecord?id=CVE-2023-52518 Référence CVE CVE-2023-52519 https://www.cve.org/CVERecord?id=CVE-2023-52519 Référence CVE CVE-2023-52520 https://www.cve.org/CVERecord?id=CVE-2023-52520 Référence CVE CVE-2023-52523 https://www.cve.org/CVERecord?id=CVE-2023-52523 Référence CVE CVE-2023-52524 https://www.cve.org/CVERecord?id=CVE-2023-52524 Référence CVE CVE-2023-52525 https://www.cve.org/CVERecord?id=CVE-2023-52525 Référence CVE CVE-2023-52528 https://www.cve.org/CVERecord?id=CVE-2023-52528 Référence CVE CVE-2023-52529 https://www.cve.org/CVERecord?id=CVE-2023-52529 Référence CVE CVE-2023-52530 https://www.cve.org/CVERecord?id=CVE-2023-52530 Référence CVE CVE-2023-52531 https://www.cve.org/CVERecord?id=CVE-2023-52531 Référence CVE CVE-2023-52532 https://www.cve.org/CVERecord?id=CVE-2023-52532 Référence CVE CVE-2023-52559 https://www.cve.org/CVERecord?id=CVE-2023-52559 Référence CVE CVE-2023-52561 https://www.cve.org/CVERecord?id=CVE-2023-52561 Référence CVE CVE-2023-52563 https://www.cve.org/CVERecord?id=CVE-2023-52563 Référence CVE CVE-2023-52564 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0329Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2023-52513 Référence CVE CVE-2023-52515 https://www.cve.org/CVERecord?id=CVE-2023-52515 Référence CVE CVE-2023-52517 https://www.cve.org/CVERecord?id=CVE-2023-52517 Référence CVE CVE-2023-52518 https://www.cve.org/CVERecord?id=CVE-2023-52518 Référence CVE CVE-2023-52519 https://www.cve.org/CVERecord?id=CVE-2023-52519 Référence CVE CVE-2023-52520 https://www.cve.org/CVERecord?id=CVE-2023-52520 Référence CVE CVE-2023-52523 https://www.cve.org/CVERecord?id=CVE-2023-52523 Référence CVE CVE-2023-52524 https://www.cve.org/CVERecord?id=CVE-2023-52524 Référence CVE CVE-2023-52525 https://www.cve.org/CVERecord?id=CVE-2023-52525 Référence CVE CVE-2023-52528 https://www.cve.org/CVERecord?id=CVE-2023-52528 Référence CVE CVE-2023-52529 https://www.cve.org/CVERecord?id=CVE-2023-52529 Référence CVE CVE-2023-52530 https://www.cve.org/CVERecord?id=CVE-2023-52530 Référence CVE CVE-2023-52531 https://www.cve.org/CVERecord?id=CVE-2023-52531 Référence CVE CVE-2023-52532 https://www.cve.org/CVERecord?id=CVE-2023-52532 Référence CVE CVE-2023-52559 https://www.cve.org/CVERecord?id=CVE-2023-52559 Référence CVE CVE-2023-52563 https://www.cve.org/CVERecord?id=CVE-2023-52563 Référence CVE CVE-2023-52564 https://www.cve.org/CVERecord?id=CVE-2023-52564 Référence CVE CVE-2023-52566 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2023-027614Linux の Linux Kernel における初期化されていないリソースの使用に関する脆弱性

Linux の Linux Kernel には、初期化されていないリソースの使用に関する脆弱性が存在します。

Official advisory ↗
03

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.
Fix availability varies by product
Affected
Fixed
Linux: < 2.6.34, 4.14.327 ≤ 4.14.*, 4.19.296 ≤ 4.19.*, 5.4.258 ≤ 5.4.*, 5.10.198 ≤ 5.10.*, 5.15.135 ≤ 5.15.*, 6.1.57 ≤ 6.1.*, 6.5.7 ≤ 6.5.*, 6.6 ≤ *
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 2 Mar 2024 · Last source change 11 May 2026, 19:29 UTC · CWE-908 · Use of Uninitialized Resource

CVE recordCVE.org · 5.2
CVSS sourceNIST NVD
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-57153
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceNIST NVD
NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

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.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2023-57153↗Vendor CSAF · SUSE Product Security Team↗CVE authority or vendor reference↗Patch or update reference↗Patch or update reference↗Patch or update 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.
Free version - for non-commercial use only.CVE-2023-52528 · cve.blacktree.nl