{"uuid": "a28dc8bd-5f26-417f-b1fe-4d98cffc0e42", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37825", "type": "seen", "source": "https://t.me/cvedetector/24802", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37825 - \"Nvidia Nvmet Out-of-Bounds Access Vulnerability\"\", \n  \"Content\": \"CVE ID : CVE-2025-37825 \nPublished : May 8, 2025, 7:15 a.m. | 2\u00a0hours, 2\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nnvmet: fix out-of-bounds access in nvmet_enable_port  \n  \nWhen trying to enable a port that has no transport configured yet,  \nnvmet_enable_port() uses NVMF_TRTYPE_MAX (255) to query the transports  \narray, causing an out-of-bounds access:  \n  \n[  106.058694] BUG: KASAN: global-out-of-bounds in nvmet_enable_port+0x42/0x1da  \n[  106.058719] Read of size 8 at addr ffffffff89dafa58 by task ln/632  \n[...]  \n[  106.076026] nvmet: transport type 255 not supported  \n  \nSince commit 200adac75888, NVMF_TRTYPE_MAX is the default state as configured by  \nnvmet_ports_make().  \nAvoid this by checking for NVMF_TRTYPE_MAX before proceeding. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"08 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-08T11:45:00.000000Z"}