Към съдържанието
Търсене

CVE-2026-74713: Linux

7.1

CVSS 3.1

Няма данни

Вероятност да бъде експлоатирана в следващите 30 дни (EPSS)

Няма потвърждение

Атакува се

Няма данни

Време до експлоатация

Атакува се локално, без особени условия, без вход и без действие от потребителя.

  • Експлоатация: няма данни за експлоатация
  • Атаката не може да се автоматизира

Описание

Оригинално описание

In the Linux kernel, the following vulnerability has been resolved: vhost_iotlb: bound map allocation in add_range vhost_iotlb_add_range_ctx() only retires an old entry when the table has a non-zero limit, has exactly reached that limit and has VHOST_IOTLB_FLAG_RETIRE set. Non-retiring tables can keep allocating entries after reaching their configured limit. Existing vhost devices allocate their IOTLB with max_iotlb_entries from vhost.c, which defaults to 2048 and is tunable by module parameter. Use the caller-provided limit at the allocation point instead of adding a separate default in the common IOTLB helper, and reject non-positive values in vhost paths that can report an error. Other vhost IOTLB users should not create zero-limit tables when entries can be populated from userspace or guest-controlled requests. Add caller-side max_iotlb_entries parameters for mlx5 vDPA, VDUSE and vhost-vDPA. Reject non-positive VDUSE and vhost-vDPA values, and require at least two entries for vdpa_sim and mlx5 vDPA paths that install full-range mappings, since those mappings are split into two IOTLB entries. Handle full-range mappings in the common helper by checking that the IOTLB can hold both split entries before inserting the first half. This avoids returning an error after leaving a half mapping behind. When the table is full, keep the existing retire behavior for retiring tables and return -ENOSPC for non-retiring tables. Reuse the retired map node instead of freeing it and allocating a replacement, so a stream of IOTLB updates cannot keep forcing GFP_ATOMIC allocations after the table has reached its limit. If a zero-limit IOTLB still reaches the common helper, treat it as a configuration error and return -EINVAL. I found this bug myself, though the patch was written with AI assistance.

Засегнати продукти

  • Linux Linux: 0bbe30668d89ec8a309f28ced6d092c90fb23e8c преди 91d3f1fcb8f7109f18d46a7366bb8202ac4b4456; 0bbe30668d89ec8a309f28ced6d092c90fb23e8c преди 96da3e1439e7d689eea09fc9b6227fbab5b88ac3; 0bbe30668d89ec8a309f28ced6d092c90fb23e8c преди eb70200e34772572ad08e99291b08afea6522111; 0bbe30668d89ec8a309f28ced6d092c90fb23e8c преди b57164cdddb46924ff9fa191b727ca097744de88; 0bbe30668d89ec8a309f28ced6d092c90fb23e8c преди ae128dd19040ee06a4f8143c7ced4d18080d7a9a; 0bbe30668d89ec8a309f28ced6d092c90fb23e8c преди 1ed35ac7f3fe2b4396bdd29ac3a7f0ebc0829e94
  • Linux Linux: 5.7; преди 5.7; 6.1.191 до 6.1.*; 6.6.160 до 6.6.*; 6.12.114 до 6.12.*; 6.18.57 до 6.18.*; 7.1.9 до 7.1.*; 7.2 до *

История

  • 22 август 2026 Публикувано

Други уязвимости в Linux Linux

Първоизточници

CVE-2026-74713: Linux | freedomonline.bg