CVE-2026-74306
HighCVSS 7.8Exploitation Probability (EPSS)
Low risk3th percentile - higher than 3% of all known CVEs
Summary
In the Linux kernel, the vfio/qat driver's qat_vf_resume_write() checks the file position before taking the migf->lock, but copies data after taking the lock and re-reading the position. Two concurrent writers can bypass the bounds check and write past the end of the migration-state buffer.
Risk Assessment
The vulnerability may lead to out-of-bounds write, potentially resulting in memory corruption and possibly privilege escalation or system crash.
Recommendation
Install the Linux kernel patch that moves the boundary checks after acquiring migf->lock, eliminating the race.
Original NVD description (English source)
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.