Answer in brief
CVE-2026-74306 records a Unknown severity vulnerability in vfio/qat: fix f_pos race in qat_vf_resume_write(). 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 | >=bb208810b1abf1c84870cfbe1cc9cf1a1d35c607 <6465af0004dc1b067129a26ef44f19cdf13bbce6 || >=bb208810b1abf1c84870cfbe1cc9cf1a1d35c607 <d416dcefdbac90d96b22485fd93f28229ad9984b || >=bb208810b1abf1c84870cfbe1cc9cf1a1d35c607 <b6fd7a40a66485c8aa8156d8fcf50b95cb8ba281 || >=bb208810b1abf1c84870cfbe1cc9cf1a1d35c607 <4ec5e932e636896e97e4c6a8205b0ac76d52421a | 6465af0004dc1b067129a26ef44f19cdf13bbce6, d416dcefdbac90d96b22485fd93f28229ad9984b, b6fd7a40a66485c8aa8156d8fcf50b95cb8ba281, 4ec5e932e636896e97e4c6a8205b0ac76d52421a |
| Linux/Linuxgeneric | 6.10 | 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: vfio/qat: fix f_pos race in qat_vf_resume_write() qat_vf_resume_write() checks filp->f_pos before taking migf->lock, but copies into the migration-state buffer after taking the lock and re-reading the shared file position. Two concurrent writers could therefore pass the bounds check with the old offset, then have the second writer copy after the first advanced f_pos, writing past the end of the migration-state buffer. Take migf->lock before doing the boundary checks.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-74306 records a Unknown severity vulnerability in vfio/qat: fix f_pos race in qat_vf_resume_write(). 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 | >=bb208810b1abf1c84870cfbe1cc9cf1a1d35c607 <6465af0004dc1b067129a26ef44f19cdf13bbce6 || >=bb208810b1abf1c84870cfbe1cc9cf1a1d35c607 <d416dcefdbac90d96b22485fd93f28229ad9984b || >=bb208810b1abf1c84870cfbe1cc9cf1a1d35c607 <b6fd7a40a66485c8aa8156d8fcf50b95cb8ba281 || >=bb208810b1abf1c84870cfbe1cc9cf1a1d35c607 <4ec5e932e636896e97e4c6a8205b0ac76d52421a | 6465af0004dc1b067129a26ef44f19cdf13bbce6, d416dcefdbac90d96b22485fd93f28229ad9984b, b6fd7a40a66485c8aa8156d8fcf50b95cb8ba281, 4ec5e932e636896e97e4c6a8205b0ac76d52421a |
| Linux/Linuxgeneric | 6.10 | 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: vfio/qat: fix f_pos race in qat_vf_resume_write() qat_vf_resume_write() checks filp->f_pos before taking migf->lock, but copies into the migration-state buffer after taking the lock and re-reading the shared file position. Two concurrent writers could therefore pass the bounds check with the old offset, then have the second writer copy after the first advanced f_pos, writing past the end of the migration-state buffer. Take migf->lock before doing the boundary checks.
Quoted source text, attributed separately from HOL analysis.