ptp: ocp: Limit signal/freq counts in summary output functions
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.12.316.14.96.15In the Linux kernel, the following vulnerability has been resolved:
ptp: ocp: Limit signal/freq counts in summary output functions
The debugfs summary output could access uninitialized elements in the freq_in[] and signal_out[] arrays, causing NULL pointer dereferences and triggering a kernel Oops (page_fault_oops). This patch adds u8 fields (nr_freq_in, nr_signal_out) to track the number of initialized elements, with a maximum of 4 per array. The summary output functions are updated to respect these limits, preventing out-of-bounds access and ensuring safe array handling.
Widen the label variables because the change confuses GCC about max length of the strings.
From the CVE record · Linux
The Linux kernel’s ptp ocp debugfs summary output can access uninitialized array elements, causing a NULL pointer dereference and kernel Oops. This can occur when the summary output processes those elements; the input does not specify attacker access requirements or user interaction.
Engineers running Linux kernels with the ptp ocp component should check their versions; affected versions were not specified.