Answer in brief
CVE-2026-74425 records a Unknown severity vulnerability in afs: handle CB.InitCallBackState3 requests without a server record. 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 | >=39ba6af83a7f9dee3e6a7916f41a48bcbda54eba <42e3917cdbdc3d35e191c525687a6d5427f237fd || >=40e8b52fe8c8ab6920ea5f59c5469b6918cce624 <cc848a080f7a6848dfeef441722419fdcbfe9b8d || >=40e8b52fe8c8ab6920ea5f59c5469b6918cce624 <0bd5f2786a878148190b4c7c259d01313d5f2357 || >=40e8b52fe8c8ab6920ea5f59c5469b6918cce624 <f3cf725cd284b7912d5522babb44721bf38c8887 | 42e3917cdbdc3d35e191c525687a6d5427f237fd, cc848a080f7a6848dfeef441722419fdcbfe9b8d, 0bd5f2786a878148190b4c7c259d01313d5f2357, f3cf725cd284b7912d5522babb44721bf38c8887 |
| Linux/Linuxgeneric | 6.15 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
In the Linux kernel, the following vulnerability has been resolved: afs: handle CB.InitCallBackState3 requests without a server record The cache manager callback path now attaches the server record to an incoming call through the rxrpc peer's app data. That association is not guaranteed to exist for every callback request, and most callback handlers already tolerate that case. Make CB.InitCallBackState3 follow the same pattern by checking whether a server record was attached before using it. If the peer is not mapped to a server record, trace the request and ignore it, matching the existing behaviour for other unmatched callback requests. This keeps the callback handler consistent with the rest of the cache manager service and avoids depending on peer state that may not be available for a given request.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-74425 records a Unknown severity vulnerability in afs: handle CB.InitCallBackState3 requests without a server record. 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 | >=39ba6af83a7f9dee3e6a7916f41a48bcbda54eba <42e3917cdbdc3d35e191c525687a6d5427f237fd || >=40e8b52fe8c8ab6920ea5f59c5469b6918cce624 <cc848a080f7a6848dfeef441722419fdcbfe9b8d || >=40e8b52fe8c8ab6920ea5f59c5469b6918cce624 <0bd5f2786a878148190b4c7c259d01313d5f2357 || >=40e8b52fe8c8ab6920ea5f59c5469b6918cce624 <f3cf725cd284b7912d5522babb44721bf38c8887 | 42e3917cdbdc3d35e191c525687a6d5427f237fd, cc848a080f7a6848dfeef441722419fdcbfe9b8d, 0bd5f2786a878148190b4c7c259d01313d5f2357, f3cf725cd284b7912d5522babb44721bf38c8887 |
| Linux/Linuxgeneric | 6.15 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
In the Linux kernel, the following vulnerability has been resolved: afs: handle CB.InitCallBackState3 requests without a server record The cache manager callback path now attaches the server record to an incoming call through the rxrpc peer's app data. That association is not guaranteed to exist for every callback request, and most callback handlers already tolerate that case. Make CB.InitCallBackState3 follow the same pattern by checking whether a server record was attached before using it. If the peer is not mapped to a server record, trace the request and ignore it, matching the existing behaviour for other unmatched callback requests. This keeps the callback handler consistent with the rest of the cache manager service and avoids depending on peer state that may not be available for a given request.
Quoted source text, attributed separately from HOL analysis.