nday
CVE-2024-35957

iommu/vt-d: Fix WARN_ON in iommu probe path

Linux / Linux

Disclosed . nday has no fix record for it yet; that does not mean no patch exists. None of the four PoC sources lists it. Not in CISA KEV.

why these tags

nday derives these tags by fixed rules from the facts below; NVD, the CNA and other sources do not assign them. Vocabulary and rules: ~/tags.

local
AV:L in CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L (CVSS 3.1) from the ADP CISA-ADP
no authentication required
PR:N in CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L (CVSS 3.1) from the ADP CISA-ADP
no user interaction
UI:N in CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L (CVSS 3.1) from the ADP CISA-ADP
Linux kernel
affected products in the CVE record: Linux · LinuxCPE names NVD's analysts give as vulnerable: o:linux:linux_kernel
operating system
affected products in the CVE record: Linux · LinuxCPE names NVD's analysts give as vulnerable: o:linux:linux_kernelthe product type of Linux kernel in nday's product registry
stage
DIS
disclosed
cvss
5.9 MEDIUM v3.1

Lifecycle

x axis UTC; dot = exact minute, wide bar = date only, hollow = unknown or inferred.
time unknown
DISdisclosed
2024-05-20T09:41Z
PATpatch
no record yet
ANAanalysis
no record yet
POCPoC
no record yet
ITWexploited
no record yet
KEVKEV
no record yet

Summary

In the Linux kernel, the following vulnerability has been resolved:

iommu/vt-d: Fix WARN_ON in iommu probe path

Commit 1a75cc710b95 ("iommu/vt-d: Use rbtree to track iommu probed devices") adds all devices probed by the iommu driver in a rbtree indexed by the source ID of each device. It assumes that each device has a unique source ID. This assumption is incorrect and the VT-d spec doesn't state this requirement either.

The reason for using a rbtree to track devices is to look up the device with PCI bus and devfunc in the paths of handling ATS invalidation time out error and the PRI I/O page faults. Both are PCI ATS feature related.

Only track the devices that have PCI ATS capabilities in the rbtree to avoid unnecessary WARN_ON in the iommu probe path. Otherwise, on some platforms below kernel splat will be displayed and the iommu probe results in failure.

WARNING: CPU: 3 PID: 166 at drivers/iommu/intel/iommu.c:158 intel_iommu_probe_device+0x319/0xd90
Call Trace:
 <TASK>
 ? __warn+0x7e/0x180
 ? intel_iommu_probe_device+0x319/0xd90
 ? report_bug+0x1f8/0x200
 ? handle_bug+0x3c/0x70
 ? exc_invalid_op+0x18/0x70
 ? asm_exc_invalid_op+0x1a/0x20
 ? intel_iommu_probe_device+0x319/0xd90
 ? debug_mutex_init+0x37/0x50
 __iommu_probe_device+0xf2/0x4f0
 iommu_probe_device+0x22/0x70
 iommu_bus_notifier+0x1e/0x40
 notifier_call_chain+0x46/0x150
 blocking_notifier_call_chain+0x42/0x60
 bus_notify+0x2f/0x50
 device_add+0x5ed/0x7e0
 platform_device_add+0xf5/0x240
 mfd_add_devices+0x3f9/0x500
 ? preempt_count_add+0x4c/0xa0
 ? up_write+0xa2/0x1b0
 ? __debugfs_create_file+0xe3/0x150
 intel_lpss_probe+0x49f/0x5b0
 ? pci_conf1_write+0xa3/0xf0
 intel_lpss_pci_probe+0xcf/0x110 [intel_lpss_pci]
 pci_device_probe+0x95/0x120
 really_probe+0xd9/0x370
 ? __pfx___driver_attach+0x10/0x10
 __driver_probe_device+0x73/0x150
 driver_probe_device+0x19/0xa0
 __driver_attach+0xb6/0x180
 ? __pfx___driver_attach+0x10/0x10
 bus_for_each_dev+0x77/0xd0
 bus_add_driver+0x114/0x210
 driver_register+0x5b/0x110
 ? __pfx_intel_lpss_pci_driver_init+0x10/0x10 [intel_lpss_pci]
 do_one_initcall+0x57/0x2b0
 ? kmalloc_trace+0x21e/0x280
 ? do_init_module+0x1e/0x210
 do_init_module+0x5f/0x210
 load_module+0x1d37/0x1fc0
 ? init_module_from_file+0x86/0xd0
 init_module_from_file+0x86/0xd0
 idempotent_init_module+0x17c/0x230
 __x64_sys_finit_module+0x56/0xb0
 do_syscall_64+0x6e/0x140
 entry_SYSCALL_64_after_hwframe+0x71/0x79

Original text of the CVE record (cvelist), shown as published.

Exploit conditions

What an attack needs, read from the CVSS vector.
Attack vector AV:L
Local: needs a local or SSH session, or a user tricked into acting on the machine
Attack complexity AC:L
Low: no special conditions; the attacker can expect repeatable success
Privileges required PR:N
None: no account or authorization needed
User interaction UI:N
None: no action by anyone other than the attacker

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

CVSS 3.1 vector from the CVE record, added by the ADP CISA-ADP.

Event log

+DISdisclosed

CVE record published by Linux. CVSS 5.9, medium.

src cvelist · nday , bulk import · raw
{
  "id": 334192,
  "type": "disclosed",
  "source": "cvelist",
  "url": "https://www.cve.org/CVERecord?id=CVE-2024-35957",
  "occurred_at": "2024-05-20T09:41:49.93Z",
  "observed_at": "2026-11-13T05:38:34.075966Z",
  "is_backfill": true,
  "dedupe_key": "",
  "detail": {
    "cvss": {
      "source": "adp:CISA-ADP",
      "vector": "CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L",
      "version": "3.1",
      "base_score": 5.9,
      "base_severity": "MEDIUM"
    },
    "ssvc": {
      "timestamp": "2024-05-20T14:23:39.677207Z",
      "automatable": "no",
      "exploitation": "none",
      "technical_impact": "partial"
    },
    "state": "PUBLISHED",
    "date_published": "2024-05-20T09:41:49.930Z",
    "assigner_short_name": "Linux"
  }
}

Report an error

report an error or omission

Something on this page wrong or missing? Tell the editors; if they accept it, this page's revision log says so publicly. Upstream data is not changed.

Researcher discussion

0 researchers mentioned this in the last 7 days

Posts on X by researchers on nday's list that mention this CVE, shown as posted. nday does not check them.

nday has not collected any post on X by listed researchers that mentions this CVE.

Discussion

0 comments

No comments yet.