Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2023-53847: usb-storage: alauda: Fix uninit-value in alauda_check_media()

Noroxi assessment

Priority: Monitor (action score 0/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.23% (FIRST EPSS).
  • Fixed version: Linux Linux 044f4446e06bb03c52216697b14867ebc555ad3b, 0d2d5282d39aed6f27dfe1ed60a5f3934ebd21cd, 153c3e85873cc3e2f387169783c3a227bad9a95a.

Low priority for now. Upgrade to Linux Linux 044f4446e06bb03c52216697b14867ebc555ad3b, 0d2d5282d39aed6f27dfe1ed60a5f3934ebd21cd, 153c3e85873cc3e2f387169783c3a227bad9a95a 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: usb-storage: alauda: Fix uninit-value in alauda_check_media() Syzbot got KMSAN to complain about access to an uninitialized value in the alauda subdriver of usb-storage: BUG: KMSAN: uninit-value in alauda_transport+0x462/0x57f0 drivers/usb/storage/alauda.c:1137 CPU: 0 PID: 12279 Comm: usb-storage Not tainted 5.3.0-rc7+ #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Call Trace: __dump_stack lib/dump_stack.c:77 [inline] dump_stack+0x191/0x1f0 lib/dump_stack.c:113 kmsan_report+0x13a/0x2b0 mm/kmsan/kmsan_report.c:108 __msan_warning+0x73/0xe0 mm/kmsan/kmsan_instr.c:250 alauda_check_media+0x344/0x3310 drivers/usb/storage/alauda.c:460 The problem is that alauda_check_media() doesn't verify that its USB transfer succeeded before trying to use the received data. What should happen if the transfer fails isn't entirely clear, but a reasonably conservative approach is to pretend that no media is present. A similar problem exists in a usb_stor_dbg() call in alauda_get_media_status(). In this case, when an error occurs the call is redundant, because usb_stor_ctrl_transfer() already will print a debugging message. Finally, unrelated to the uninitialized memory access, is the fact that alauda_check_media() performs DMA to a buffer on the stack. Fortunately usb-storage provides a general purpose DMA-able buffer for uses like this. We'll use it instead.

—No exploit Fix available
Published
Dec 9, 2025
Updated
Jun 17, 2026
EPSS
0.2% · 15th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

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.

Follow CVE-2023-53847

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

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 help

Affected 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.

—

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

    • 2.6.16affected
    • e80b0fade09ef1ee67b0898d480d4c588f124d5f and later · before 153c3e85873cc3e2f387169783c3a227bad9a95aaffected · git
    • e80b0fade09ef1ee67b0898d480d4c588f124d5f and later · before 49d380bcd6cba987c6085fae6464c9c087e8d9a0affected · git
    • e80b0fade09ef1ee67b0898d480d4c588f124d5f and later · before 044f4446e06bb03c52216697b14867ebc555ad3baffected · git
    • e80b0fade09ef1ee67b0898d480d4c588f124d5f and later · before fe7c3a445d22783d27fe8bd0521a8aab1eb9da65affected · git
    • e80b0fade09ef1ee67b0898d480d4c588f124d5f and later · before 7a11d1e2625bdb2346f6586773b20b20977278acaffected · git
    • e80b0fade09ef1ee67b0898d480d4c588f124d5f and later · before 0d2d5282d39aed6f27dfe1ed60a5f3934ebd21cdaffected · git
    • e80b0fade09ef1ee67b0898d480d4c588f124d5f and later · before 373e0ab8c4c516561493f1acf367c7ee7dc053c2affected · git
    • e80b0fade09ef1ee67b0898d480d4c588f124d5f and later · before a6ff6e7a9dd69364547751db0f626a10a6d628d2affected · git
    • before 2.6.16not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.52-16.1.52-1
Debian:13linuxbefore 6.4.11-16.4.11-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2023-53844Dec 9, 2025 · drm/ttm: Don't leak a resource on swapout move error
    31Monitor
  • ← EarlierCVE-2023-53845Dec 9, 2025 · nilfs2: fix infinite loop in nilfs_mdt_get_block()
    0Monitor
  • Later →CVE-2023-53848Dec 9, 2025 · md/raid5-cache: fix a deadlock in r5l_exit_log()
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux044f4446e06bb03c52216697b14867ebc555ad3bVendor (CNA)
Linux Linux0d2d5282d39aed6f27dfe1ed60a5f3934ebd21cdVendor (CNA)
Linux Linux153c3e85873cc3e2f387169783c3a227bad9a95aVendor (CNA)
Linux Linux373e0ab8c4c516561493f1acf367c7ee7dc053c2Vendor (CNA)
Linux Linux49d380bcd6cba987c6085fae6464c9c087e8d9a0Vendor (CNA)
Linux Linux7a11d1e2625bdb2346f6586773b20b20977278acVendor (CNA)
Linux Linuxa6ff6e7a9dd69364547751db0f626a10a6d628d2Vendor (CNA)
Linux Linuxfe7c3a445d22783d27fe8bd0521a8aab1eb9da65Vendor (CNA)
debian:linux6.1.52-1 · Debian:12Package 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.

No history yet (it accumulates with the daily EPSS job).

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 researchers

Finders, 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

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

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

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records