In the Linux kernel, the following vulnerability has been resolved: net: arcnet: com20020: Fix null-ptr-deref in com20020pci_probe() During driver initialization, the pointer of card info, i.e. the variable 'ci' is required. However, the definition of 'com20020pci_id_table' reveals that this field is empty for some devices, which will cause null pointer dereference when initializing these devices. The following log reveals it: [ 3.973806] KASAN: null-ptr-deref in range [0x0000000000000028-0x000000000000002f] [ 3.973819] RIP: 0010:com20020pci_probe+0x18d/0x13e0 [com20020_pci] [ 3.975181] Call Trace: [ 3.976208] local_pci_probe+0x13f/0x210 [ 3.977248] pci_device_probe+0x34c/0x6d0 [ 3.977255] ? pci_uevent+0x470/0x470 [ 3.978265] really_probe+0x24c/0x8d0 [ 3.978273] __driver_probe_device+0x1b3/0x280 [ 3.979288] driver_probe_device+0x50/0x370 Fix this by checking whether the 'ci' is a null pointer first.

The Unity Linux 20 host has a package installed that is affected by a vulnerability as referenced in the UTSA-2025-989252 advisory.

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

    net: arcnet: com20020: Fix null-ptr-deref in com20020pci_probe()

    During driver initialization, the pointer of card info, i.e. the     variable 'ci' is required. However, the definition of     'com20020pci_id_table' reveals that this field is empty for some     devices, which will cause null pointer dereference when initializing     these devices.

    The following log reveals it:

    [    3.973806] KASAN: null-ptr-deref in range [0x0000000000000028-0x000000000000002f]     [    3.973819] RIP: 0010:com20020pci_probe+0x18d/0x13e0 [com20020_pci]     [    3.975181] Call Trace:
    [    3.976208]  local_pci_probe+0x13f/0x210     [    3.977248]  pci_device_probe+0x34c/0x6d0     [    3.977255]  ? pci_uevent+0x470/0x470     [    3.978265]  really_probe+0x24c/0x8d0     [    3.978273]  __driver_probe_device+0x1b3/0x280     [    3.979288]  driver_probe_device+0x50/0x370

    Fix this by checking whether the 'ci' is a null pointer first.

Tenable has extracted the preceding description block directly from the Unity Linux security advisory.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The Unity Linux 20 host has a package installed that is affected by a vulnerability as referenced in the UTSA-2025-986726 advisory.

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

    net: arcnet: com20020: Fix null-ptr-deref in com20020pci_probe()

    During driver initialization, the pointer of card info, i.e. the     variable 'ci' is required. However, the definition of     'com20020pci_id_table' reveals that this field is empty for some     devices, which will cause null pointer dereference when initializing     these devices.

    The following log reveals it:

    [    3.973806] KASAN: null-ptr-deref in range [0x0000000000000028-0x000000000000002f]     [    3.973819] RIP: 0010:com20020pci_probe+0x18d/0x13e0 [com20020_pci]     [    3.975181] Call Trace:
    [    3.976208]  local_pci_probe+0x13f/0x210     [    3.977248]  pci_device_probe+0x34c/0x6d0     [    3.977255]  ? pci_uevent+0x470/0x470     [    3.978265]  really_probe+0x24c/0x8d0     [    3.978273]  __driver_probe_device+0x1b3/0x280     [    3.979288]  driver_probe_device+0x50/0x370

    Fix this by checking whether the 'ci' is a null pointer first.

Tenable has extracted the preceding description block directly from the Unity Linux security advisory.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - net: arcnet: com20020: Fix null-ptr-deref in com20020pci_probe() During driver initialization, the pointer     of card info, i.e. the variable 'ci' is required. However, the definition of 'com20020pci_id_table'     reveals that this field is empty for some devices, which will cause null pointer dereference when     initializing these devices. The following log reveals it: [ 3.973806] KASAN: null-ptr-deref in range     [0x0000000000000028-0x000000000000002f] [ 3.973819] RIP: 0010:com20020pci_probe+0x18d/0x13e0     [com20020_pci] [ 3.975181] Call Trace: [ 3.976208] local_pci_probe+0x13f/0x210 [ 3.977248]     pci_device_probe+0x34c/0x6d0 [ 3.977255] ? pci_uevent+0x470/0x470 [ 3.978265] really_probe+0x24c/0x8d0 [     3.978273] __driver_probe_device+0x1b3/0x280 [ 3.979288] driver_probe_device+0x50/0x370 Fix this by     checking whether the 'ci' is a null pointer first. (CVE-2022-48908)

Note that Nessus relies on the presence of the package as reported by the vendor.

ID	Name	Product	Family	Severity
273570	Unity Linux 20.1070a Security Update: kernel (UTSA-2025-989252)	Nessus	Unity Linux Local Security Checks	medium
269153	Unity Linux 20.1070e Security Update: kernel (UTSA-2025-986726)	Nessus	Unity Linux Local Security Checks	medium
248770	Linux Distros Unpatched Vulnerability : CVE-2022-48908	Nessus	Misc.	medium

Detections

Analytics

CVE-2022-48908

medium

Tenable Plugins

medium

medium

medium