Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2023-53998: hwrng: virtio - Fix race on data_avail and actual data

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.21% (FIRST EPSS).
  • Fixed version: Linux Linux 22c30022cde6e2c88612b3a499223cfa912f1bc7, 241ef15776a7c8505008db689175b320d345ecd3, 2fc91f156b3f3446a1bce80cf4adedcbf41271c2.

Low priority for now. Upgrade to Linux Linux 22c30022cde6e2c88612b3a499223cfa912f1bc7, 241ef15776a7c8505008db689175b320d345ecd3, 2fc91f156b3f3446a1bce80cf4adedcbf41271c2 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: hwrng: virtio - Fix race on data_avail and actual data The virtio rng device kicks off a new entropy request whenever the data available reaches zero. When a new request occurs at the end of a read operation, that is, when the result of that request is only needed by the next reader, then there is a race between the writing of the new data and the next reader. This is because there is no synchronisation whatsoever between the writer and the reader. Fix this by writing data_avail with smp_store_release and reading it with smp_load_acquire when we first enter read. The subsequent reads are safe because they're either protected by the first load acquire, or by the completion mechanism. Also remove the redundant zeroing of data_idx in random_recv_done (data_idx must already be zero at this point) and data_avail in request_entropy (ditto).

—No exploit Fix available
Published
Dec 24, 2025
Updated
Jun 17, 2026
EPSS
0.2% · 11th 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-53998

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.26affected
    • f7f510ec195781c857ab76366a3e1c59e1caae42 and later · before 241ef15776a7c8505008db689175b320d345ecd3affected · git
    • f7f510ec195781c857ab76366a3e1c59e1caae42 and later · before a43bcb0b661cbbf3ad797d2aee6b6fd06b8fc69daffected · git
    • f7f510ec195781c857ab76366a3e1c59e1caae42 and later · before 77471e4912d3960dafe141e268c44be8024fe4dcaffected · git
    • f7f510ec195781c857ab76366a3e1c59e1caae42 and later · before c76d991b6f01a5d931e7053a73bc9524975a5215affected · git
    • f7f510ec195781c857ab76366a3e1c59e1caae42 and later · before 22c30022cde6e2c88612b3a499223cfa912f1bc7affected · git
    • f7f510ec195781c857ab76366a3e1c59e1caae42 and later · before 318657b4c2077289659f1cd9e2a34f6a3b208e3eaffected · git
    • f7f510ec195781c857ab76366a3e1c59e1caae42 and later · before 2fc91f156b3f3446a1bce80cf4adedcbf41271c2affected · git
    • f7f510ec195781c857ab76366a3e1c59e1caae42 and later · before ac52578d6e8d300dd50f790f29a24169b1edd26caffected · git
    • before 2.6.26not 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.4-16.4.4-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-53996Dec 24, 2025 · x86/sev: Make enc_dec_hypercall() accept a size instead of npages
    37Monitor
  • ← EarlierCVE-2023-53997Dec 24, 2025 · thermal: of: fix double-free on unregistration
    31Monitor
  • Later →CVE-2023-54000Dec 24, 2025 · net: hns3: fix deadlock issue when externel_lb and reset are executed together
    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 Linux22c30022cde6e2c88612b3a499223cfa912f1bc7Vendor (CNA)
Linux Linux241ef15776a7c8505008db689175b320d345ecd3Vendor (CNA)
Linux Linux2fc91f156b3f3446a1bce80cf4adedcbf41271c2Vendor (CNA)
Linux Linux318657b4c2077289659f1cd9e2a34f6a3b208e3eVendor (CNA)
Linux Linux77471e4912d3960dafe141e268c44be8024fe4dcVendor (CNA)
Linux Linuxa43bcb0b661cbbf3ad797d2aee6b6fd06b8fc69dVendor (CNA)
Linux Linuxac52578d6e8d300dd50f790f29a24169b1edd26cVendor (CNA)
Linux Linuxc76d991b6f01a5d931e7053a73bc9524975a5215Vendor (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