Answer in brief
CVE-2024-49999 records a Unknown severity vulnerability in afs: Fix the setting of the server responding flag. 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 | >=98f9fda2057ba34b720c4d353351024d6dcee90f <3d51ab44123f35dd1d646d99a15ebef10f55e263 || >=98f9fda2057ba34b720c4d353351024d6dcee90f <97c953572d98080c5f1486155350bb688041747a || >=98f9fda2057ba34b720c4d353351024d6dcee90f <ff98751bae40faed1ba9c6a7287e84430f7dec64 | 3d51ab44123f35dd1d646d99a15ebef10f55e263, 97c953572d98080c5f1486155350bb688041747a, ff98751bae40faed1ba9c6a7287e84430f7dec64 |
| Linux/Linuxgeneric | 6.8 | Not reported |
Published upstream
Oct 21, 2024
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: afs: Fix the setting of the server responding flag In afs_wait_for_operation(), we set transcribe the call responded flag to the server record that we used after doing the fileserver iteration loop - but it's possible to exit the loop having had a response from the server that we've discarded (e.g. it returned an abort or we started receiving data, but the call didn't complete). This means that op->server might be NULL, but we don't check that before attempting to set the server flag.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2024-49999 records a Unknown severity vulnerability in afs: Fix the setting of the server responding flag. 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 | >=98f9fda2057ba34b720c4d353351024d6dcee90f <3d51ab44123f35dd1d646d99a15ebef10f55e263 || >=98f9fda2057ba34b720c4d353351024d6dcee90f <97c953572d98080c5f1486155350bb688041747a || >=98f9fda2057ba34b720c4d353351024d6dcee90f <ff98751bae40faed1ba9c6a7287e84430f7dec64 | 3d51ab44123f35dd1d646d99a15ebef10f55e263, 97c953572d98080c5f1486155350bb688041747a, ff98751bae40faed1ba9c6a7287e84430f7dec64 |
| Linux/Linuxgeneric | 6.8 | Not reported |
Published upstream
Oct 21, 2024
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: afs: Fix the setting of the server responding flag In afs_wait_for_operation(), we set transcribe the call responded flag to the server record that we used after doing the fileserver iteration loop - but it's possible to exit the loop having had a response from the server that we've discarded (e.g. it returned an abort or we started receiving data, but the call didn't complete). This means that op->server might be NULL, but we don't check that before attempting to set the server flag.
Quoted source text, attributed separately from HOL analysis.