NewStart CGSL MAIN 7.02 : kernel Multiple Vulnerabilities (NS-SA-2025-0118)

high Nessus Plugin ID 242830

Synopsis

The remote NewStart CGSL host is affected by multiple vulnerabilities.

Description

The remote NewStart CGSL host, running version MAIN 7.02, has kernel packages installed that are affected by multiple vulnerabilities:

- In the Linux kernel, the following vulnerability has been resolved: smack: tcp: ipv4, fix incorrect labeling Currently, Smack mirrors the label of incoming tcp/ipv4 connections: when a label 'foo' connects to a label 'bar' with tcp/ipv4, 'foo' always gets 'foo' in returned ipv4 packets. So, 1) returned packets are incorrectly labeled ('foo' instead of 'bar') 2) 'bar' can write to 'foo' without being authorized to write. Here is a scenario how to see this: * Take two machines, let's call them C and S, with active Smack in the default state (no settings, no rules, no labeled hosts, only builtin labels) * At S, add Smack rule 'foo bar w' (labels 'foo' and 'bar' are instantiated at S at this moment) * At S, at label 'bar', launch a program that listens for incoming tcp/ipv4 connections * From C, at label 'foo', connect to the listener at S. (label 'foo' is instantiated at C at this moment) Connection succeedes and works. * Send some data in both directions. * Collect network traffic of this connection. All packets in both directions are labeled with the CIPSO of the label 'foo'. Hence, label 'bar' writes to 'foo' without being authorized, and even without ever being known at C. If anybody cares: exactly the same happens with DCCP. This behavior 1st manifested in release 2.6.29.4 (see Fixes below) and it looks unintentional. At least, no explanation was provided. I changed returned packes label into the 'bar', to bring it into line with the Smack documentation claims. (CVE-2024-47659)

- In the Linux kernel, the following vulnerability has been resolved: HID: logitech-hidpp: Fix kernel crash on receiver USB disconnect hidpp_connect_event() has *four* time-of-check vs time-of-use (TOCTOU) races when it races with itself. hidpp_connect_event() primarily runs from a workqueue but it also runs on probe() and if a device-connected packet is received by the hw when the thread running hidpp_connect_event() from probe() is waiting on the hw, then a second thread running hidpp_connect_event() will be started from the workqueue. This opens the following races (note the below code is simplified): 1. Retrieving + printing the protocol (harmless race): if (!hidpp->protocol_major) { hidpp_root_get_protocol_version() hidpp->protocol_major = response.rap.params[0]; } We can actually see this race hit in the dmesg in the abrt output attached to rhbz#2227968: [ 3064.624215] logitech-hidpp- device 0003:046D:4071.0049: HID++ 4.5 device connected. [ 3064.658184] logitech-hidpp-device 0003:046D:4071.0049: HID++ 4.5 device connected. Testing with extra logging added has shown that after this the 2 threads take turn grabbing the hw access mutex (send_mutex) so they ping-pong through all the other TOCTOU cases managing to hit all of them: 2. Updating the name to the HIDPP name (harmless race): if (hidpp->name == hdev->name) { ... hidpp->name = new_name; } 3. Initializing the power_supply class for the battery (problematic!): hidpp_initialize_battery() { if (hidpp->battery.ps) return 0; probe_battery(); /* Blocks, threads take turns executing this */ hidpp->battery.desc.properties = devm_kmemdup(dev, hidpp_battery_props, cnt, GFP_KERNEL); hidpp->battery.ps = devm_power_supply_register(&hidpp->hid_dev->dev, &hidpp->battery.desc, cfg); } 4. Creating delayed input_device (potentially problematic): if (hidpp->delayed_input) return; hidpp->delayed_input = hidpp_allocate_input(hdev); The really big problem here is 3. Hitting the race leads to the following sequence: hidpp->battery.desc.properties = devm_kmemdup(dev, hidpp_battery_props, cnt, GFP_KERNEL);
hidpp->battery.ps = devm_power_supply_register(&hidpp->hid_dev->dev, &hidpp->battery.desc, cfg); ...
hidpp->battery.desc.properties = devm_kmemdup(dev, hidpp_battery_props, cnt, GFP_KERNEL);
hidpp->battery.ps = devm_power_supply_register(&hidpp->hid_dev->dev, &hidpp->battery.desc, cfg); So now we have registered 2 power supplies for the same battery, which looks a bit weird from userspace's pov but this is not even the really big problem. Notice how: 1. This is all devm-maganaged 2. The hidpp->battery.desc struct is shared between the 2 power supplies 3. hidpp->battery.desc.properties points to the result from the second devm_kmemdup() This causes a use after free scenario on USB disconnect of the receiver: 1. The last registered power supply class device gets unregistered 2. The memory from the last devm_kmemdup() call gets freed, hidpp->battery.desc.properties now points to freed memory 3. The first registered power supply class device gets unregistered, this involves sending a remove uevent to userspace which invokes power_supply_uevent() to fill the uevent data 4. power_supply_uevent() uses hidpp->battery.desc.properties which now points to freed memory leading to backtraces like this one: Sep 22 20:01:35 eric kernel: BUG: unable to handle page fault for address: ffffb2140e017f08 ... Sep 22 20:01:35 eric kernel: Workqueue: usb_hub_wq hub_event Sep 22 20:01:35 eric kernel: RIP:
0010:power_supply_uevent+0xee/0x1d0 ... Sep 22 20:01:35 eric kernel: ? asm_exc_page_fault+0x26/0x30 Sep 22 20:01:35 eric kernel: ? power_supply_uevent+0xee/0x1d0 Sep 22 20:01:35 eric kernel: ? power_supply_uevent+0x10d/0x1d0 Sep 22 20:01:35 eric kernel: dev_uevent+0x10f/0x2d0 Sep 22 20:01:35 eric kernel: kobject_uevent_env+0x291/0x680 Sep 22 20:01:35 eric kernel: ---truncated--- (CVE-2023-52478)

- In the Linux kernel, the following vulnerability has been resolved: clk: sunxi-ng: h6: Reparent CPUX during PLL CPUX rate change While PLL CPUX clock rate change when CPU is running from it works in vast majority of cases, now and then it causes instability. This leads to system crashes and other undefined behaviour. After a lot of testing (30+ hours) while also doing a lot of frequency switches, we can't observe any instability issues anymore when doing reparenting to stable clock like 24 MHz oscillator.
(CVE-2023-52882)

- In the Linux kernel, the following vulnerability has been resolved: net: can: j1939: enhanced error handling for tightly received RTS messages in xtp_rx_rts_session_new This patch enhances error handling in scenarios with RTS (Request to Send) messages arriving closely. It replaces the less informative WARN_ON_ONCE backtraces with a new error handling method. This provides clearer error messages and allows for the early termination of problematic sessions. Previously, sessions were only released at the end of j1939_xtp_rx_rts(). Potentially this could be reproduced with something like: testj1939 -r vcan0:0x80 & while true; do # send first RTS cansend vcan0 18EC8090#1014000303002301; # send second RTS cansend vcan0 18EC8090#1014000303002301; # send abort cansend vcan0 18EC8090#ff00000000002301; done (CVE-2023-52887)

- In the Linux kernel, the following vulnerability has been resolved: media: mediatek: vcodec: Only free buffer VA that is not NULL In the MediaTek vcodec driver, while mtk_vcodec_mem_free() is mostly called only when the buffer to free exists, there are some instances that didn't do the check and triggered warnings in practice. We believe those checks were forgotten unintentionally. Add the checks back to fix the warnings. (CVE-2023-52888)

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

Solution

Upgrade the vulnerable CGSL kernel packages. Note that updated packages may not be available yet. Please contact ZTE for more information.

Plugin Details

Severity: High

ID: 242830

File Name: newstart_cgsl_NS-SA-2025-0118_kernel.nasl

Version: 1.1

Type: local

Family: NewStart CGSL Local Security Checks

Published: 7/25/2025

Updated: 7/25/2025

Supported Sensors: Nessus

Risk Information

VPR

Risk Factor: Critical

Score: 9.0

CVSS v2

Risk Factor: High

Base Score: 9

Temporal Score: 7.4

Vector: CVSS2#AV:N/AC:L/Au:S/C:C/I:C/A:C

CVSS Score Source: CVE-2024-47659

CVSS v3

Risk Factor: High

Base Score: 8.8

Temporal Score: 8.2

Vector: CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Temporal Vector: CVSS:3.0/E:F/RL:O/RC:C

Vulnerability Information

CPE: p-cpe:/a:zte:cgsl_main:bpftool, p-cpe:/a:zte:cgsl_main:kernel-tools, p-cpe:/a:zte:cgsl_main:perf, p-cpe:/a:zte:cgsl_main:kernel-headers, p-cpe:/a:zte:cgsl_main:kernel, p-cpe:/a:zte:cgsl_main:kernel-tools-libs, cpe:/o:zte:cgsl_main:7, p-cpe:/a:zte:cgsl_main:kernel-devel, p-cpe:/a:zte:cgsl_main:kernel-core, p-cpe:/a:zte:cgsl_main:kernel-modules, p-cpe:/a:zte:cgsl_main:python3-perf, p-cpe:/a:zte:cgsl_main:kernel-modules-extra

Required KB Items: Host/local_checks_enabled, Host/cpu, Host/ZTE-CGSL/release, Host/ZTE-CGSL/rpm-list

Exploit Available: true

Exploit Ease: Exploits are available

Patch Publication Date: 7/25/2025

Vulnerability Publication Date: 7/21/2021

CISA Known Exploited Vulnerability Due Dates: 2/26/2025, 3/25/2025

Reference Information

CVE: CVE-2023-52478, CVE-2023-52882, CVE-2023-52887, CVE-2023-52888, CVE-2023-52926, CVE-2024-24858, CVE-2024-24859, CVE-2024-26952, CVE-2024-26984, CVE-2024-27012, CVE-2024-27022, CVE-2024-27398, CVE-2024-27399, CVE-2024-27401, CVE-2024-31076, CVE-2024-33619, CVE-2024-33621, CVE-2024-33847, CVE-2024-34030, CVE-2024-34777, CVE-2024-35247, CVE-2024-35871, CVE-2024-35915, CVE-2024-35932, CVE-2024-35933, CVE-2024-35949, CVE-2024-36012, CVE-2024-36013, CVE-2024-36015, CVE-2024-36016, CVE-2024-36017, CVE-2024-36026, CVE-2024-36031, CVE-2024-36270, CVE-2024-36281, CVE-2024-36286, CVE-2024-36476, CVE-2024-36477, CVE-2024-36478, CVE-2024-36479, CVE-2024-36481, CVE-2024-36489, CVE-2024-36880, CVE-2024-36881, CVE-2024-36883, CVE-2024-36889, CVE-2024-36890, CVE-2024-36894, CVE-2024-36895, CVE-2024-36896, CVE-2024-36899, CVE-2024-36901, CVE-2024-36902, CVE-2024-36903, CVE-2024-36904, CVE-2024-36905, CVE-2024-36908, CVE-2024-36913, CVE-2024-36914, CVE-2024-36916, CVE-2024-36918, CVE-2024-36919, CVE-2024-36921, CVE-2024-36922, CVE-2024-36923, CVE-2024-36924, CVE-2024-36928, CVE-2024-36929, CVE-2024-36931, CVE-2024-36933, CVE-2024-36938, CVE-2024-36940, CVE-2024-36941, CVE-2024-36946, CVE-2024-36947, CVE-2024-36950, CVE-2024-36951, CVE-2024-36952, CVE-2024-36959, CVE-2024-36960, CVE-2024-36964, CVE-2024-36965, CVE-2024-36968, CVE-2024-36969, CVE-2024-36974, CVE-2024-36975, CVE-2024-36977, CVE-2024-36978, CVE-2024-36979, CVE-2024-37021, CVE-2024-37078, CVE-2024-37354, CVE-2024-37356, CVE-2024-38384, CVE-2024-38390, CVE-2024-38538, CVE-2024-38539, CVE-2024-38541, CVE-2024-38543, CVE-2024-38544, CVE-2024-38545, CVE-2024-38550, CVE-2024-38551, CVE-2024-38552, CVE-2024-38555, CVE-2024-38556, CVE-2024-38557, CVE-2024-38558, CVE-2024-38559, CVE-2024-38560, CVE-2024-38561, CVE-2024-38562, CVE-2024-38564, CVE-2024-38567, CVE-2024-38570, CVE-2024-38571, CVE-2024-38575, CVE-2024-38576, CVE-2024-38577, CVE-2024-38578, CVE-2024-38579, CVE-2024-38581, CVE-2024-38583, CVE-2024-38585, CVE-2024-38586, CVE-2024-38588, CVE-2024-38589, CVE-2024-38590, CVE-2024-38591, CVE-2024-38593, CVE-2024-38594, CVE-2024-38596, CVE-2024-38597, CVE-2024-38598, CVE-2024-38599, CVE-2024-38601, CVE-2024-38604, CVE-2024-38607, CVE-2024-38610, CVE-2024-38614, CVE-2024-38616, CVE-2024-38617, CVE-2024-38619, CVE-2024-38622, CVE-2024-38623, CVE-2024-38624, CVE-2024-38625, CVE-2024-38627, CVE-2024-38628, CVE-2024-38629, CVE-2024-38630, CVE-2024-38632, CVE-2024-38634, CVE-2024-38636, CVE-2024-38659, CVE-2024-38664, CVE-2024-38780, CVE-2024-39276, CVE-2024-39282, CVE-2024-39296, CVE-2024-39298, CVE-2024-39301, CVE-2024-39371, CVE-2024-39461, CVE-2024-39462, CVE-2024-39463, CVE-2024-39464, CVE-2024-39466, CVE-2024-39467, CVE-2024-39468, CVE-2024-39469, CVE-2024-39470, CVE-2024-39471, CVE-2024-39473, CVE-2024-39474, CVE-2024-39475, CVE-2024-39476, CVE-2024-39479, CVE-2024-39480, CVE-2024-39481, CVE-2024-39483, CVE-2024-39484, CVE-2024-39485, CVE-2024-39486, CVE-2024-39487, CVE-2024-39488, CVE-2024-39489, CVE-2024-39490, CVE-2024-39493, CVE-2024-39494, CVE-2024-39496, CVE-2024-39497, CVE-2024-39499, CVE-2024-39503, CVE-2024-39504, CVE-2024-39506, CVE-2024-39508, CVE-2024-39509, CVE-2024-40900, CVE-2024-40902, CVE-2024-40905, CVE-2024-40906, CVE-2024-40908, CVE-2024-40910, CVE-2024-40911, CVE-2024-40912, CVE-2024-40913, CVE-2024-40914, CVE-2024-40915, CVE-2024-40916, CVE-2024-40919, CVE-2024-40922, CVE-2024-40923, CVE-2024-40924, CVE-2024-40925, CVE-2024-40928, CVE-2024-40929, CVE-2024-40934, CVE-2024-40935, CVE-2024-40936, CVE-2024-40937, CVE-2024-40938, CVE-2024-40939, CVE-2024-40940, CVE-2024-40941, CVE-2024-40942, CVE-2024-40943, CVE-2024-40944, CVE-2024-40948, CVE-2024-40951, CVE-2024-40952, CVE-2024-40953, CVE-2024-40956, CVE-2024-40957, CVE-2024-40959, CVE-2024-40960, CVE-2024-40961, CVE-2024-40962, CVE-2024-40963, CVE-2024-40965, CVE-2024-40967, CVE-2024-40969, CVE-2024-40970, CVE-2024-40971, CVE-2024-40972, CVE-2024-40974, CVE-2024-40978, CVE-2024-40980, CVE-2024-40983, CVE-2024-40984, CVE-2024-40987, CVE-2024-40988, CVE-2024-40989, CVE-2024-40990, CVE-2024-40992, CVE-2024-40994, CVE-2024-40995, CVE-2024-41001, CVE-2024-41004, CVE-2024-41005, CVE-2024-41007, CVE-2024-41009, CVE-2024-41010, CVE-2024-41011, CVE-2024-41012, CVE-2024-41013, CVE-2024-41014, CVE-2024-41018, CVE-2024-41019, CVE-2024-41020, CVE-2024-41021, CVE-2024-41025, CVE-2024-41027, CVE-2024-41028, CVE-2024-41030, CVE-2024-41031, CVE-2024-41034, CVE-2024-41035, CVE-2024-41036, CVE-2024-41037, CVE-2024-41039, CVE-2024-41040, CVE-2024-41041, CVE-2024-41042, CVE-2024-41044, CVE-2024-41046, CVE-2024-41047, CVE-2024-41048, CVE-2024-41049, CVE-2024-41050, CVE-2024-41053, CVE-2024-41054, CVE-2024-41055, CVE-2024-41056, CVE-2024-41059, CVE-2024-41060, CVE-2024-41062, CVE-2024-41063, CVE-2024-41064, CVE-2024-41065, CVE-2024-41066, CVE-2024-41069, CVE-2024-41072, CVE-2024-41073, CVE-2024-41074, CVE-2024-41075, CVE-2024-41076, CVE-2024-41077, CVE-2024-41078, CVE-2024-41081, CVE-2024-41084, CVE-2024-41087, CVE-2024-41089, CVE-2024-41090, CVE-2024-41091, CVE-2024-41092, CVE-2024-41094, CVE-2024-41095, CVE-2024-41096, CVE-2024-41097, CVE-2024-42063, CVE-2024-42069, CVE-2024-42070, CVE-2024-42073, CVE-2024-42074, CVE-2024-42076, CVE-2024-42077, CVE-2024-42079, CVE-2024-42080, CVE-2024-42082, CVE-2024-42084, CVE-2024-42085, CVE-2024-42090, CVE-2024-42093, CVE-2024-42094, CVE-2024-42095, CVE-2024-42096, CVE-2024-42098, CVE-2024-42104, CVE-2024-42105, CVE-2024-42106, CVE-2024-42109, CVE-2024-42110, CVE-2024-42113, CVE-2024-42114, CVE-2024-42115, CVE-2024-42122, CVE-2024-42124, CVE-2024-42128, CVE-2024-42129, CVE-2024-42132, CVE-2024-42133, CVE-2024-42137, CVE-2024-42138, CVE-2024-42140, CVE-2024-42142, CVE-2024-42144, CVE-2024-42145, CVE-2024-42148, CVE-2024-42156, CVE-2024-42160, CVE-2024-42161, CVE-2024-42224, CVE-2024-42225, CVE-2024-42228, CVE-2024-42229, CVE-2024-42232, CVE-2024-42236, CVE-2024-42237, CVE-2024-42239, CVE-2024-42241, CVE-2024-42243, CVE-2024-42244, CVE-2024-42246, CVE-2024-42248, CVE-2024-42250, CVE-2024-42253, CVE-2024-42258, CVE-2024-42265, CVE-2024-42267, CVE-2024-42268, CVE-2024-42269, CVE-2024-42270, CVE-2024-42271, CVE-2024-42273, CVE-2024-42274, CVE-2024-42280, CVE-2024-42281, CVE-2024-42283, CVE-2024-42284, CVE-2024-42285, CVE-2024-42286, CVE-2024-42288, CVE-2024-42289, CVE-2024-42290, CVE-2024-42292, CVE-2024-42301, CVE-2024-42304, CVE-2024-42305, CVE-2024-42306, CVE-2024-42308, CVE-2024-42309, CVE-2024-42318, CVE-2024-42321, CVE-2024-42322, CVE-2024-43098, CVE-2024-43823, CVE-2024-43829, CVE-2024-43830, CVE-2024-43839, CVE-2024-43853, CVE-2024-43857, CVE-2024-43860, CVE-2024-43861, CVE-2024-43864, CVE-2024-43866, CVE-2024-43867, CVE-2024-43868, CVE-2024-43870, CVE-2024-43875, CVE-2024-43876, CVE-2024-43877, CVE-2024-43879, CVE-2024-43880, CVE-2024-43881, CVE-2024-43882, CVE-2024-43884, CVE-2024-43889, CVE-2024-43892, CVE-2024-43905, CVE-2024-44931, CVE-2024-44934, CVE-2024-44938, CVE-2024-44941, CVE-2024-44946, CVE-2024-44971, CVE-2024-44977, CVE-2024-44988, CVE-2024-44995, CVE-2024-44999, CVE-2024-45008, CVE-2024-45828, CVE-2024-46677, CVE-2024-46714, CVE-2024-46722, CVE-2024-46724, CVE-2024-46725, CVE-2024-46731, CVE-2024-46743, CVE-2024-46745, CVE-2024-46756, CVE-2024-46758, CVE-2024-46765, CVE-2024-46777, CVE-2024-46791, CVE-2024-46800, CVE-2024-46804, CVE-2024-46812, CVE-2024-46814, CVE-2024-46815, CVE-2024-46818, CVE-2024-46819, CVE-2024-46840, CVE-2024-46857, CVE-2024-47141, CVE-2024-47659, CVE-2024-49569, CVE-2024-49571, CVE-2024-49867, CVE-2024-49946, CVE-2024-49951, CVE-2024-49965, CVE-2024-50051, CVE-2024-50112, CVE-2024-50131, CVE-2024-50180, CVE-2024-50193, CVE-2024-50222, CVE-2024-50242, CVE-2024-50246, CVE-2024-50269, CVE-2024-50276, CVE-2024-50302, CVE-2024-52559, CVE-2024-53104, CVE-2024-53108, CVE-2024-53126, CVE-2024-53155, CVE-2024-53165, CVE-2024-53191, CVE-2024-53687, CVE-2024-53690, CVE-2024-54456, CVE-2024-55639, CVE-2024-55916, CVE-2024-56369, CVE-2024-56538, CVE-2024-56581, CVE-2024-56626, CVE-2024-56627, CVE-2024-56704, CVE-2024-56719, CVE-2024-56759, CVE-2024-56765, CVE-2024-56767, CVE-2024-56769, CVE-2024-56770, CVE-2024-56778, CVE-2024-56779, CVE-2024-56787, CVE-2024-57791, CVE-2024-57792, CVE-2024-57798, CVE-2024-57801, CVE-2024-57802, CVE-2024-57807, CVE-2024-57841, CVE-2024-57849, CVE-2024-57874, CVE-2024-57882, CVE-2024-57884, CVE-2024-57885, CVE-2024-57888, CVE-2024-57890, CVE-2024-57892, CVE-2024-57893, CVE-2024-57897, CVE-2024-57899, CVE-2024-57901, CVE-2024-57903, CVE-2024-57904, CVE-2024-57906, CVE-2024-57907, CVE-2024-57908, CVE-2024-57910, CVE-2024-57913, CVE-2024-57916, CVE-2024-57917, CVE-2024-57922, CVE-2024-57925, CVE-2024-57926, CVE-2024-57931, CVE-2024-57932, CVE-2024-57933, CVE-2024-57938, CVE-2024-57939, CVE-2024-57940, CVE-2024-57945, CVE-2024-57946, CVE-2024-57949, CVE-2024-57977, CVE-2024-57979, CVE-2024-57981, CVE-2024-57986, CVE-2024-58001, CVE-2024-58002, CVE-2024-58005, CVE-2024-58007, CVE-2024-58010, CVE-2024-58051, CVE-2024-58052, CVE-2024-58053, CVE-2024-58054, CVE-2024-58055, CVE-2024-58056, CVE-2024-58058, CVE-2024-58061, CVE-2024-58063, CVE-2024-58068, CVE-2024-58069, CVE-2024-58070, CVE-2024-58071, CVE-2024-58072, CVE-2024-58076, CVE-2024-58077, CVE-2024-58080, CVE-2024-58083, CVE-2024-58086, CVE-2024-58087, CVE-2024-58088, CVE-2025-21629, CVE-2025-21632, CVE-2025-21639, CVE-2025-21642, CVE-2025-21645, CVE-2025-21646, CVE-2025-21648, CVE-2025-21653, CVE-2025-21654, CVE-2025-21656, CVE-2025-21658, CVE-2025-21663, CVE-2025-21664, CVE-2025-21665, CVE-2025-21666, CVE-2025-21670, CVE-2025-21673, CVE-2025-21674, CVE-2025-21676, CVE-2025-21682, CVE-2025-21684, CVE-2025-21689, CVE-2025-21694, CVE-2025-21699, CVE-2025-21704, CVE-2025-21705, CVE-2025-21707, CVE-2025-21711, CVE-2025-21716, CVE-2025-21718, CVE-2025-21719, CVE-2025-21724, CVE-2025-21731, CVE-2025-21733, CVE-2025-21734, CVE-2025-21735, CVE-2025-21736, CVE-2025-21738, CVE-2025-21743, CVE-2025-21744, CVE-2025-21750, CVE-2025-21756, CVE-2025-21767, CVE-2025-21772, CVE-2025-21775, CVE-2025-21776, CVE-2025-21779, CVE-2025-21780, CVE-2025-21781, CVE-2025-21782, CVE-2025-21783, CVE-2025-21785, CVE-2025-21787, CVE-2025-21789, CVE-2025-21790, CVE-2025-21792, CVE-2025-21793, CVE-2025-21795, CVE-2025-21796, CVE-2025-21799, CVE-2025-21802, CVE-2025-21806, CVE-2025-21808, CVE-2025-21810, CVE-2025-21812, CVE-2025-21814, CVE-2025-21823, CVE-2025-21828, CVE-2025-21830, CVE-2025-21832, CVE-2025-21835, CVE-2025-21838, CVE-2025-21846, CVE-2025-21847, CVE-2025-21848, CVE-2025-21855, CVE-2025-21856, CVE-2025-21857, CVE-2025-21858, CVE-2025-21866, CVE-2025-21993

Detections

Analytics