CVE REMEDIATION GUIDE
Review reviewHighFixed-version data available

CVE-2025-38416 remediation guide

Linux Linux, linux kernel, debian linux

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...

Open CVE record
ProductLinux Linux, linux kernel, debian linux
Affected versions>= 9961127d4bce6325e9a0b0fb105e0c85a6c62cb7 < a514fca2b8e95838a3ba600f31a18fa60b76d893, >= 9961127d4bce6325e9a0b0fb105e0c85a6c62cb7 < 000bfbc6bc334a93fffca8f5aa9583e7b6356cb5, >= 9961127d4bce6325e9a0b0fb105e0c85a6c62cb7 < ac6992f72bd8e22679c1e147ac214de6a7093c23, >= 9961127d4bce6325e9a0b0fb105e0c85a6c62cb7 < dc7722619a9c307e9938d735cf4a2210d3d48dcb, >= 9961127d4bce6325e9a0b0fb105e0c85a6c62cb7 < a8acc7080ad55c5402a1b818b3008998247dda87, >= 9961127d4bce6325e9a0b0fb105e0c85a6c62cb7 < 55c3dbd8389636161090a2b2b6d2d709b9602e9c, >= 9961127d4bce6325e9a0b0fb105e0c85a6c62cb7 < e9799db771b2d574d5bf0dfb3177485e5f40d4d6, >= 9961127d4bce6325e9a0b0fb105e0c85a6c62cb7 < fc27ab48904ceb7e4792f0c400f1ef175edf16fe, >= 4.2, >= 4.2 < 5.4.295, >= 5.5 < 5.10.239, >= 5.11 < 5.15.186, >= 5.16 < 6.1.142, >= 6.2 < 6.6.95, >= 6.7 < 6.12.35, >= 6.13 < 6.15.4, 6.16, 11.0
Fixed versions5.4.295, 5.10.239, 5.15.186, 6.1.142, 6.6.95, 6.12.35, 6.15.4
Priority basisReview · CVSS 7.8 · EPSS 0.18%
01

Identify the affected asset

Confirm whether Linux Linux, linux kernel, debian linux is installed, record the deployed version and installation path, and identify exposed interfaces.

  • Record the product name, package or appliance identifier, and installed version.
  • Identify internet-facing, administrative, API, and internal access paths.
  • Preserve the pre-change configuration and relevant service logs.
02

Validate the affected-version match

Compare the deployed version with the affected range: >= 9961127d4bce6325e9a0b0fb105e0c85a6c62cb7 < a514fca2b8e95838a3ba600f31a18fa60b76d893, >= 9961127d4bce6325e9a0b0fb105e0c85a6c62cb7 < 000bfbc6bc334a93fffca8f5aa9583e7b6356cb5, >= 9961127d4bce6325e9a0b0fb105e0c85a6c62cb7 < ac6992f72bd8e22679c1e147ac214de6a7093c23, >= 9961127d4bce6325e9a0b0fb105e0c85a6c62cb7 < dc7722619a9c307e9938d735cf4a2210d3d48dcb, >= 9961127d4bce6325e9a0b0fb105e0c85a6c62cb7 < a8acc7080ad55c5402a1b818b3008998247dda87, >= 9961127d4bce6325e9a0b0fb105e0c85a6c62cb7 < 55c3dbd8389636161090a2b2b6d2d709b9602e9c, >= 9961127d4bce6325e9a0b0fb105e0c85a6c62cb7 < e9799db771b2d574d5bf0dfb3177485e5f40d4d6, >= 9961127d4bce6325e9a0b0fb105e0c85a6c62cb7 < fc27ab48904ceb7e4792f0c400f1ef175edf16fe, >= 4.2, >= 4.2 < 5.4.295, >= 5.5 < 5.10.239, >= 5.11 < 5.15.186, >= 5.16 < 6.1.142, >= 6.2 < 6.6.95, >= 6.7 < 6.12.35, >= 6.13 < 6.15.4, 6.16, 11.0. Treat incomplete inventory results as unresolved.

03

Prioritize with independent signals

The CVSS severity warrants an early asset and exposure review. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

04

Apply supported remediation

Follow the vendor advisory or supported update path. Current fixed-version status: 5.4.295, 5.10.239, 5.15.186, 6.1.142, 6.6.95, 6.12.35, 6.15.4. Preserve configuration and rollback material before change.

05

Verify the result

Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.

  • Confirm the expected version and package state.
  • Run a functional health check for critical service paths.
  • Review authentication, error, application, and security monitoring logs.
  • Reassess exposure if the supported fix cannot be applied.

Operational boundary

This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.

CVE-2025-38416 Remediation Guide | SECUFOCUS NOW