Answer in brief
CVE-2022-50394 records a High severity (CVSS 7.8) vulnerability in i2c: ismt: Fix an out-of-bounds bug in ismt_access(). 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.
Answer in brief
CVE-2022-50394 records a High severity (CVSS 7.8) vulnerability in i2c: ismt: Fix an out-of-bounds bug in ismt_access(). 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.
CVSS is 7.8. 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.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=13f35ac14cd0a9a1c4f0034c4c40d0ae98844ce9 <4a7bb1d93addb2f67e36fed00a53cb7f270d7b7a || >=13f35ac14cd0a9a1c4f0034c4c40d0ae98844ce9 <03b7ef7a6c5ca1ff553470166b4919db88b810f6 || >=13f35ac14cd0a9a1c4f0034c4c40d0ae98844ce9 <bfe41d966c860a8ad4c735639d616da270c92735 || >=13f35ac14cd0a9a1c4f0034c4c40d0ae98844ce9 <cdcbae2c5003747ddfd14e29db9c1d5d7e7c44dd || >=13f35ac14cd0a9a1c4f0034c4c40d0ae98844ce9 <9ac541a0898e8ec187a3fa7024b9701cffae6bf2 || >=13f35ac14cd0a9a1c4f0034c4c40d0ae98844ce9 <96c12fd0ec74641295e1c3c34dea3dce1b6c3422 || >=13f35ac14cd0a9a1c4f0034c4c40d0ae98844ce9 <a642469d464b2780a25a49b51ae56623c65eac34 || >=13f35ac14cd0a9a1c4f0034c4c40d0ae98844ce9 <233348a04becf133283f0076e20b317302de21d9 || >=13f35ac14cd0a9a1c4f0034c4c40d0ae98844ce9 <39244cc754829bf707dccd12e2ce37510f5b1f8d | 4a7bb1d93addb2f67e36fed00a53cb7f270d7b7a, 03b7ef7a6c5ca1ff553470166b4919db88b810f6, bfe41d966c860a8ad4c735639d616da270c92735, cdcbae2c5003747ddfd14e29db9c1d5d7e7c44dd, 9ac541a0898e8ec187a3fa7024b9701cffae6bf2, 96c12fd0ec74641295e1c3c34dea3dce1b6c3422, a642469d464b2780a25a49b51ae56623c65eac34, 233348a04becf133283f0076e20b317302de21d9, 39244cc754829bf707dccd12e2ce37510f5b1f8d |
| Linux/Linuxgeneric | 3.9 | Not reported |
Published upstream
Sep 18, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
In the Linux kernel, the following vulnerability has been resolved: i2c: ismt: Fix an out-of-bounds bug in ismt_access() When the driver does not check the data from the user, the variable 'data->block[0]' may be very large to cause an out-of-bounds bug. The following log can reveal it: [ 33.995542] i2c i2c-1: ioctl, cmd=0x720, arg=0x7ffcb3dc3a20 [ 33.995978] ismt_smbus 0000:00:05.0: I2C_SMBUS_BLOCK_DATA: WRITE [ 33.996475] ================================================================== [ 33.996995] BUG: KASAN: out-of-bounds in ismt_access.cold+0x374/0x214b [ 33.997473] Read of size 18446744073709551615 at addr ffff88810efcfdb1 by task ismt_poc/485 [ 33.999450] Call Trace: [ 34.001849] memcpy+0x20/0x60 [ 34.002077] ismt_access.cold+0x374/0x214b [ 34.003382] __i2c_smbus_xfer+0x44f/0xfb0 [ 34.004007] i2c_smbus_xfer+0x10a/0x390 [ 34.004291] i2cdev_ioctl_smbus+0x2c8/0x710 [ 34.005196] i2cdev_ioctl+0x5ec/0x74c Fix this bug by checking the size of 'data->block[0]' first.
Quoted source text, attributed separately from HOL analysis.
CVSS is 7.8. 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.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=13f35ac14cd0a9a1c4f0034c4c40d0ae98844ce9 <4a7bb1d93addb2f67e36fed00a53cb7f270d7b7a || >=13f35ac14cd0a9a1c4f0034c4c40d0ae98844ce9 <03b7ef7a6c5ca1ff553470166b4919db88b810f6 || >=13f35ac14cd0a9a1c4f0034c4c40d0ae98844ce9 <bfe41d966c860a8ad4c735639d616da270c92735 || >=13f35ac14cd0a9a1c4f0034c4c40d0ae98844ce9 <cdcbae2c5003747ddfd14e29db9c1d5d7e7c44dd || >=13f35ac14cd0a9a1c4f0034c4c40d0ae98844ce9 <9ac541a0898e8ec187a3fa7024b9701cffae6bf2 || >=13f35ac14cd0a9a1c4f0034c4c40d0ae98844ce9 <96c12fd0ec74641295e1c3c34dea3dce1b6c3422 || >=13f35ac14cd0a9a1c4f0034c4c40d0ae98844ce9 <a642469d464b2780a25a49b51ae56623c65eac34 || >=13f35ac14cd0a9a1c4f0034c4c40d0ae98844ce9 <233348a04becf133283f0076e20b317302de21d9 || >=13f35ac14cd0a9a1c4f0034c4c40d0ae98844ce9 <39244cc754829bf707dccd12e2ce37510f5b1f8d | 4a7bb1d93addb2f67e36fed00a53cb7f270d7b7a, 03b7ef7a6c5ca1ff553470166b4919db88b810f6, bfe41d966c860a8ad4c735639d616da270c92735, cdcbae2c5003747ddfd14e29db9c1d5d7e7c44dd, 9ac541a0898e8ec187a3fa7024b9701cffae6bf2, 96c12fd0ec74641295e1c3c34dea3dce1b6c3422, a642469d464b2780a25a49b51ae56623c65eac34, 233348a04becf133283f0076e20b317302de21d9, 39244cc754829bf707dccd12e2ce37510f5b1f8d |
| Linux/Linuxgeneric | 3.9 | Not reported |
Published upstream
Sep 18, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
In the Linux kernel, the following vulnerability has been resolved: i2c: ismt: Fix an out-of-bounds bug in ismt_access() When the driver does not check the data from the user, the variable 'data->block[0]' may be very large to cause an out-of-bounds bug. The following log can reveal it: [ 33.995542] i2c i2c-1: ioctl, cmd=0x720, arg=0x7ffcb3dc3a20 [ 33.995978] ismt_smbus 0000:00:05.0: I2C_SMBUS_BLOCK_DATA: WRITE [ 33.996475] ================================================================== [ 33.996995] BUG: KASAN: out-of-bounds in ismt_access.cold+0x374/0x214b [ 33.997473] Read of size 18446744073709551615 at addr ffff88810efcfdb1 by task ismt_poc/485 [ 33.999450] Call Trace: [ 34.001849] memcpy+0x20/0x60 [ 34.002077] ismt_access.cold+0x374/0x214b [ 34.003382] __i2c_smbus_xfer+0x44f/0xfb0 [ 34.004007] i2c_smbus_xfer+0x10a/0x390 [ 34.004291] i2cdev_ioctl_smbus+0x2c8/0x710 [ 34.005196] i2cdev_ioctl+0x5ec/0x74c Fix this bug by checking the size of 'data->block[0]' first.
Quoted source text, attributed separately from HOL analysis.