Vulnerability Description
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.
CVSS Score
HIGH
References
- https://git.kernel.org/stable/c/4ec5e932e636896e97e4c6a8205b0ac76d52421a
- https://git.kernel.org/stable/c/6465af0004dc1b067129a26ef44f19cdf13bbce6
- https://git.kernel.org/stable/c/b6fd7a40a66485c8aa8156d8fcf50b95cb8ba281
- https://git.kernel.org/stable/c/d416dcefdbac90d96b22485fd93f28229ad9984b
FAQ
What is CVE-2026-74306?
CVE-2026-74306 is a vulnerability with a CVSS score of 7.8 (HIGH). 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 in...
How severe is CVE-2026-74306?
CVE-2026-74306 has been rated HIGH with a CVSS base score of 7.8/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-74306?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.