Answer in brief
CVE-2025-38416 records a Unknown severity vulnerability in NFC: nci: uart: Set tty->disc_data only in success path. 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-2025-38416 records a Unknown severity vulnerability in NFC: nci: uart: Set tty->disc_data only in success path. 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.
A CVSS score is not reported in the current record. 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.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=9961127d4bce6325e9a0b0fb105e0c85a6c62cb7 <a514fca2b8e95838a3ba600f31a18fa60b76d893 || >=9961127d4bce6325e9a0b0fb105e0c85a6c62cb7 <000bfbc6bc334a93fffca8f5aa9583e7b6356cb5 || >=9961127d4bce6325e9a0b0fb105e0c85a6c62cb7 <ac6992f72bd8e22679c1e147ac214de6a7093c23 || >=9961127d4bce6325e9a0b0fb105e0c85a6c62cb7 <dc7722619a9c307e9938d735cf4a2210d3d48dcb || >=9961127d4bce6325e9a0b0fb105e0c85a6c62cb7 <a8acc7080ad55c5402a1b818b3008998247dda87 || >=9961127d4bce6325e9a0b0fb105e0c85a6c62cb7 <55c3dbd8389636161090a2b2b6d2d709b9602e9c || >=9961127d4bce6325e9a0b0fb105e0c85a6c62cb7 <e9799db771b2d574d5bf0dfb3177485e5f40d4d6 || >=9961127d4bce6325e9a0b0fb105e0c85a6c62cb7 <fc27ab48904ceb7e4792f0c400f1ef175edf16fe | a514fca2b8e95838a3ba600f31a18fa60b76d893, 000bfbc6bc334a93fffca8f5aa9583e7b6356cb5, ac6992f72bd8e22679c1e147ac214de6a7093c23, dc7722619a9c307e9938d735cf4a2210d3d48dcb, a8acc7080ad55c5402a1b818b3008998247dda87, 55c3dbd8389636161090a2b2b6d2d709b9602e9c, e9799db771b2d574d5bf0dfb3177485e5f40d4d6, fc27ab48904ceb7e4792f0c400f1ef175edf16fe |
| Linux/Linuxgeneric | 4.2 | Not reported |
Published upstream
Jul 25, 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 5, 2026
In the Linux kernel, the following vulnerability has been resolved: NFC: nci: uart: Set tty->disc_data only in success path Setting tty->disc_data before opening the NCI device means we need to clean it up on error paths. This also opens some short window if device starts sending data, even before NCIUARTSETDRIVER IOCTL succeeded (broken hardware?). Close the window by exposing tty->disc_data only on the success path, when opening of the NCI device and try_module_get() succeeds. The code differs in error path in one aspect: tty->disc_data won't be ever assigned thus NULL-ified. This however should not be relevant difference, because of "tty->disc_data=NULL" in nci_uart_tty_open().
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. 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.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=9961127d4bce6325e9a0b0fb105e0c85a6c62cb7 <a514fca2b8e95838a3ba600f31a18fa60b76d893 || >=9961127d4bce6325e9a0b0fb105e0c85a6c62cb7 <000bfbc6bc334a93fffca8f5aa9583e7b6356cb5 || >=9961127d4bce6325e9a0b0fb105e0c85a6c62cb7 <ac6992f72bd8e22679c1e147ac214de6a7093c23 || >=9961127d4bce6325e9a0b0fb105e0c85a6c62cb7 <dc7722619a9c307e9938d735cf4a2210d3d48dcb || >=9961127d4bce6325e9a0b0fb105e0c85a6c62cb7 <a8acc7080ad55c5402a1b818b3008998247dda87 || >=9961127d4bce6325e9a0b0fb105e0c85a6c62cb7 <55c3dbd8389636161090a2b2b6d2d709b9602e9c || >=9961127d4bce6325e9a0b0fb105e0c85a6c62cb7 <e9799db771b2d574d5bf0dfb3177485e5f40d4d6 || >=9961127d4bce6325e9a0b0fb105e0c85a6c62cb7 <fc27ab48904ceb7e4792f0c400f1ef175edf16fe | a514fca2b8e95838a3ba600f31a18fa60b76d893, 000bfbc6bc334a93fffca8f5aa9583e7b6356cb5, ac6992f72bd8e22679c1e147ac214de6a7093c23, dc7722619a9c307e9938d735cf4a2210d3d48dcb, a8acc7080ad55c5402a1b818b3008998247dda87, 55c3dbd8389636161090a2b2b6d2d709b9602e9c, e9799db771b2d574d5bf0dfb3177485e5f40d4d6, fc27ab48904ceb7e4792f0c400f1ef175edf16fe |
| Linux/Linuxgeneric | 4.2 | Not reported |
Published upstream
Jul 25, 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 5, 2026
In the Linux kernel, the following vulnerability has been resolved: NFC: nci: uart: Set tty->disc_data only in success path Setting tty->disc_data before opening the NCI device means we need to clean it up on error paths. This also opens some short window if device starts sending data, even before NCIUARTSETDRIVER IOCTL succeeded (broken hardware?). Close the window by exposing tty->disc_data only on the success path, when opening of the NCI device and try_module_get() succeeds. The code differs in error path in one aspect: tty->disc_data won't be ever assigned thus NULL-ified. This however should not be relevant difference, because of "tty->disc_data=NULL" in nci_uart_tty_open().
Quoted source text, attributed separately from HOL analysis.