In the Linux kernel, the following vulnerability has been resolved:
crypto: seqiv - Handle EBUSY correctly
As it is seqiv only handles the special return value of EINPROGERSS,
which means that in all other cases it will free data related to the
request.
However, as the caller of seqiv may specify MAY_BACKLOG, we also need
to expect EBUSY and treat it in the same way. Otherwise backlogged
requests will trigger a use-after-free.
Security readout for executives and security teams
Plain-English summary
CVE-2023-53373 is a Linux kernel memory-safety flaw in the crypto seqiv component. A local user could potentially trigger a use-after-free, risking full confidentiality, integrity, and availability impact on the affected host. It is not listed as CISA KEV, and the provided sources do not show active exploitation.
Executive priority
Treat as high priority for Linux fleets where local users or workloads are not fully trusted. It is less urgent than a remotely exploitable KEV issue, but kernel privilege-impact bugs can become serious in shared infrastructure.
Technical view
The seqiv crypto code mishandled EBUSY for requests using MAY_BACKLOG. It freed request-related data when the request could still be backlogged, creating a CWE-416 use-after-free. The CVSS 3.1 score is 7.8 with local access, low complexity, low privileges, no user interaction, and high CIA impact.
Likely exposure
Exposure is mainly Linux systems running affected kernel versions or downstream kernels that have not incorporated the referenced stable fixes. The attack vector is local, so risk is higher on multi-user systems, shared servers, container hosts, and environments allowing untrusted local workloads.
Exploitation context
The source bundle marks KEV as false and provides no cited evidence of exploitation in the wild. Exploitation requires local access with low privileges, but successful exploitation could have severe host impact due to kernel-level memory corruption.
Researcher notes
Public details identify the root cause and stable kernel commits, but the bundle does not include exploitability proof, affected distribution package mappings, or runtime prerequisites beyond seqiv/MAY_BACKLOG behavior. Use distro advisories for precise exposure decisions.
Mitigation direction
Apply vendor Linux kernel updates that include the referenced seqiv EBUSY handling fix.
Prioritize multi-user systems, container hosts, and servers running untrusted local code.
If updates are delayed, reduce untrusted local access and workload co-tenancy.
Track distribution advisories for backported fixes and exact package versions.
Validation and detection
Inventory Linux kernel versions across servers, endpoints, appliances, and images.
Compare installed kernels with vendor advisories and the CVE record.
Confirm the relevant stable kernel fix is present or backported.
Validate golden images and container hosts are rebuilt with patched kernels.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-416: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
9Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-416 · source CWE mapping
Use After Free
Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.