Answer in brief
CVE-2023-53373 records a Unknown severity vulnerability in crypto: seqiv - Handle EBUSY correctly. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2023-53373 records a Unknown severity vulnerability in crypto: seqiv - Handle EBUSY correctly. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=0a270321dbf948963aeb0e8382fe17d2c2eb3771 <cc4d0d4251748a8a68026938f4055d2ac47c5719 || >=0a270321dbf948963aeb0e8382fe17d2c2eb3771 <1effbddaff60eeef8017c6dea1ee0ed970164d14 || >=0a270321dbf948963aeb0e8382fe17d2c2eb3771 <63551e4b7cbcd9914258827699eb2cb6ed6e4a16 || >=0a270321dbf948963aeb0e8382fe17d2c2eb3771 <ae849d2f48019ff9c104e32bf588ccbfb200e971 || >=0a270321dbf948963aeb0e8382fe17d2c2eb3771 <36ec108b7bd7e280edb22de028467bd09d644620 || >=0a270321dbf948963aeb0e8382fe17d2c2eb3771 <4d497e8b200a175094e0ac252ed878add39b8771 || >=0a270321dbf948963aeb0e8382fe17d2c2eb3771 <9477db935eb690f697d9bcc4f608927841bc8b36 || >=0a270321dbf948963aeb0e8382fe17d2c2eb3771 <32e62025e5e52fbe4812ef044759de7010b15dbc | cc4d0d4251748a8a68026938f4055d2ac47c5719, 1effbddaff60eeef8017c6dea1ee0ed970164d14, 63551e4b7cbcd9914258827699eb2cb6ed6e4a16, ae849d2f48019ff9c104e32bf588ccbfb200e971, 36ec108b7bd7e280edb22de028467bd09d644620, 4d497e8b200a175094e0ac252ed878add39b8771, 9477db935eb690f697d9bcc4f608927841bc8b36, 32e62025e5e52fbe4812ef044759de7010b15dbc |
| Linux/Linuxgeneric | 2.6.25 | Not reported |
Published upstream
Sep 18, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=0a270321dbf948963aeb0e8382fe17d2c2eb3771 <cc4d0d4251748a8a68026938f4055d2ac47c5719 || >=0a270321dbf948963aeb0e8382fe17d2c2eb3771 <1effbddaff60eeef8017c6dea1ee0ed970164d14 || >=0a270321dbf948963aeb0e8382fe17d2c2eb3771 <63551e4b7cbcd9914258827699eb2cb6ed6e4a16 || >=0a270321dbf948963aeb0e8382fe17d2c2eb3771 <ae849d2f48019ff9c104e32bf588ccbfb200e971 || >=0a270321dbf948963aeb0e8382fe17d2c2eb3771 <36ec108b7bd7e280edb22de028467bd09d644620 || >=0a270321dbf948963aeb0e8382fe17d2c2eb3771 <4d497e8b200a175094e0ac252ed878add39b8771 || >=0a270321dbf948963aeb0e8382fe17d2c2eb3771 <9477db935eb690f697d9bcc4f608927841bc8b36 || >=0a270321dbf948963aeb0e8382fe17d2c2eb3771 <32e62025e5e52fbe4812ef044759de7010b15dbc | cc4d0d4251748a8a68026938f4055d2ac47c5719, 1effbddaff60eeef8017c6dea1ee0ed970164d14, 63551e4b7cbcd9914258827699eb2cb6ed6e4a16, ae849d2f48019ff9c104e32bf588ccbfb200e971, 36ec108b7bd7e280edb22de028467bd09d644620, 4d497e8b200a175094e0ac252ed878add39b8771, 9477db935eb690f697d9bcc4f608927841bc8b36, 32e62025e5e52fbe4812ef044759de7010b15dbc |
| Linux/Linuxgeneric | 2.6.25 | Not reported |
Published upstream
Sep 18, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.