In the Linux kernel, the following vulnerability has been resolved:
i2c: virtio: disable timeout handling
If a timeout is hit, it can result is incorrect data on the I2C bus
and/or memory corruptions in the guest since the device can still be
operating on the buffers it was given while the guest has freed them.
Here is, for example, the start of a slub_debug splat which was
triggered on the next transfer after one transfer was forced to timeout
by setting a breakpoint in the backend (rust-vmm/vhost-device):
BUG kmalloc-1k (Not tainted): Poison overwritten
First byte 0x1 instead of 0x6b
Allocated in virtio_i2c_xfer+0x65/0x35c age=350 cpu=0 pid=29
__kmalloc+0xc2/0x1c9
virtio_i2c_xfer+0x65/0x35c
__i2c_transfer+0x429/0x57d
i2c_transfer+0x115/0x134
i2cdev_ioctl_rdwr+0x16a/0x1de
i2cdev_ioctl+0x247/0x2ed
vfs_ioctl+0x21/0x30
sys_ioctl+0xb18/0xb41
Freed in virtio_i2c_xfer+0x32e/0x35c age=244 cpu=0 pid=29
kfree+0x1bd/0x1cc
virtio_i2c_xfer+0x32e/0x35c
__i2c_transfer+0x429/0x57d
i2c_transfer+0x115/0x134
i2cdev_ioctl_rdwr+0x16a/0x1de
i2cdev_ioctl+0x247/0x2ed
vfs_ioctl+0x21/0x30
sys_ioctl+0xb18/0xb41
There is no simple fix for this (the driver would have to always create
bounce buffers and hold on to them until the device eventually returns
the buffers), so just disable the timeout support for now.
Security readout for executives and security teams
Plain-English summary
This Linux kernel flaw affects virtio I2C handling in virtualized environments. A transfer timeout could leave a virtual device still using memory that the guest already freed, causing corrupted I2C data or guest memory corruption. Business urgency depends on whether affected kernels use virtio-i2c.
Executive priority
Handle as a targeted infrastructure hygiene issue, not a broad emergency. Prioritize patch validation where Linux virtualization stacks use virtio I2C. If virtio-i2c is absent, document non-exposure and continue normal kernel update cadence.
Technical view
The virtio-i2c driver timeout path could free transfer buffers while the backend device continued operating on them. The kernel fix disables timeout handling because a complete safe fix would require persistent bounce buffers until device completion. The source documents memory corruption evidence from slub_debug after a forced backend timeout.
Likely exposure
Exposure appears limited to Linux guests or systems using the virtio I2C driver on affected kernel versions listed in the CVE data. General Linux systems without virtio-i2c usage are less likely to be exposed. Distribution backports may change practical exposure.
Exploitation context
The source bundle does not show active exploitation, CISA KEV listing, public exploit availability, or remote attack details. The documented trigger involved forcing a backend timeout during testing. Treat exploitability as environment-dependent and unproven from these sources.
Researcher notes
Evidence supports a guest memory corruption condition caused by unsafe timeout cleanup in virtio_i2c_xfer. The published remediation disables timeout support rather than redesigning buffer lifetime. The bundle lacks CVSS, CWE, exploit status, and distribution-specific package ranges, so exposure validation must be local.
Mitigation direction
Update to a vendor or distribution kernel containing the linked upstream stable fixes.
Prioritize virtualized systems using virtio-i2c or exposing I2C device access to guests.
Check Linux distribution advisories for backported fixes and affected package versions.
Avoid assuming a workaround unless your vendor documents one.
Track kernels in the 5.15 and 5.16 affected range named by the CVE data.
Validation and detection
Inventory hosts and guests for loaded or built virtio-i2c support.
Map running kernel versions against vendor advisories and the linked stable commits.
Confirm patched kernels include the change disabling virtio-i2c timeout handling.
Review virtualization configurations for virtio I2C devices assigned to guests.
Monitor kernel logs for I2C transfer errors or memory corruption indicators.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2021-47561 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.