UBUNTU-CVE-2025-68222: Low severity ubuntu/linux-hwe-edge vulnerability

Q: Which systems are most likely to experience this issue?

The reported failure occurs on systems using the NXP S32CC pin controller, with the example shown on an NXP S32G3 Reference Design Board. It can affect drivers that depend on pinctrl device-tree configuration, including the shown i.MX I2C driver probe path.

Q: What are the observable symptoms?

Symptoms include intermittent allocation warnings during device probing, followed by pin configuration parsing failures. Dependent drivers may then fail to probe or operate correctly.

Q: Is this an externally exploitable security issue?

The provided information describes an uninitialized-memory condition that causes allocation and device-tree pin configuration parse failures. It does not provide evidence of remote exploitation, privilege requirements, or code execution.

Q: What change resolves the issue?

The resolution initializes all fields in s32_pinctrl_desc, including num_custom_params, rather than leaving fields uninitialized after allocation with devm_kmalloc().

Published Dec 16, 2025

Updated

In the Linux kernel, the following vulnerability has been resolved: pinctrl: s32cc: fix uninitialized memory in s32pinctrldesc s32pinctrldesc is allocated with devmkmalloc(), but not all of its fields are initialized. Notably, numcustomparams is used in pinconfgenericparsedtconfig(), resulting in intermittent allocation errors, such as the following splat when probing i2c-imx: WARNING: CPU: 0 PID: 176 at mm/pagealloc.c:4795 allocpagesnoprof+0x290/0x300 [...] Hardware name: NXP S32G3 Reference Design Board 3 (S32G-VNP-RDB3) (DT) [...] Call trace: allocpagesnoprof+0x290/0x300 (P) kmalloclargenode+0x84/0x168 kmalloclargenodenoprof+0x34/0x120 kmallocnoprof+0x2ac/0x378 pinconfgenericparsedtconfig+0x68/0x1a0 s32dtnodetomap+0x104/0x248 dttomaponeconfig+0x154/0x1d8 pinctrldttomap+0x12c/0x280 createpinctrl+0x6c/0x270 pinctrlget+0xc0/0x170 devmpinctrlget+0x50/0xa0 pinctrlbindpins+0x60/0x2a0 reallyprobe+0x60/0x3a0 [...] platformdriverregister+0x2c/0x40 i2cadapimxinit+0x28/0xff8 [i2cimx] [...] This results in later parse failures that can cause issues in dependent drivers: s32g-siul2-pinctrl 4009c240.pinctrl: /soc@0/pinctrl@4009c240/i2c0-pins/i2c0-grp0: could not parse node property s32g-siul2-pinctrl 4009c240.pinctrl: /soc@0/pinctrl@4009c240/i2c0-pins/i2c0-grp0: could not parse node property [...] pca953x 0-0022: failed writing register: -6 i2c i2c-0: IMX I2C adapter registered s32g-siul2-pinctrl 4009c240.pinctrl: /soc@0/pinctrl@4009c240/i2c2-pins/i2c2-grp0: could not parse node property s32g-siul2-pinctrl 4009c240.pinctrl: /soc@0/pinctrl@4009c240/i2c2-pins/i2c2-grp0: could not parse node property i2c i2c-1: IMX I2C adapter registered s32g-siul2-pinctrl 4009c240.pinctrl: /soc@0/pinctrl@4009c240/i2c4-pins/i2c4-grp0: could not parse node property s32g-siul2-pinctrl 4009c240.pinctrl: /soc@0/pinctrl@4009c240/i2c4-pins/i2c4-grp0: could not parse node property i2c i2c-2: IMX I2C adapter registered Fix this by initializing s32pinctrldesc with devmkzalloc() instead of devmkmalloc() in s32pinctrlprobe(), which sets the previously uninitialized fields to zero.

Affected Software

150 affected componentsFixes available

ubuntu/linux-hwe-edge*

ubuntu/linux-aws-5.0*

ubuntu/linux-aws-5.3*

ubuntu/linux-azure*

ubuntu/linux-azure-5.3*

ubuntu/linux-azure-edge*

ubuntu/linux-gcp*

ubuntu/linux-gcp-5.3*

ubuntu/linux-gke-4.15*

ubuntu/linux-gke-5.4*

ubuntu/linux-gkeop-5.4*

ubuntu/linux-hwe*

ubuntu/linux-hwe-edge*

ubuntu/linux-oem*

ubuntu/linux-oracle-5.0*

ubuntu/linux-oracle-5.3*

ubuntu/linux-aws-5.11*

ubuntu/linux-aws-5.13*

ubuntu/linux-aws-5.8*

ubuntu/linux-azure-5.11*

ubuntu/linux-azure-5.13*

ubuntu/linux-azure-5.8*

ubuntu/linux-azure-fde*

ubuntu/linux-gcp-5.11*

ubuntu/linux-gcp-5.13*

ubuntu/linux-gcp-5.8*

ubuntu/linux-gke*

ubuntu/linux-gke-5.15*

ubuntu/linux-gkeop*

ubuntu/linux-gkeop-5.15*

ubuntu/linux-hwe-5.11*

ubuntu/linux-hwe-5.13*

ubuntu/linux-hwe-5.8*

ubuntu/linux-intel-5.13*

ubuntu/linux-oem-5.10*

ubuntu/linux-oem-5.13*

ubuntu/linux-oem-5.6*

ubuntu/linux-oracle-5.11*

ubuntu/linux-oracle-5.13*

ubuntu/linux-oracle-5.8*

ubuntu/linux-raspi2*

ubuntu/linux-riscv*

ubuntu/linux-riscv-5.11*

ubuntu/linux-riscv-5.8*

ubuntu/linux-allwinner-5.19*

ubuntu/linux-aws-5.19*

ubuntu/linux-aws-6.2*

ubuntu/linux-aws-6.5*

ubuntu/linux-aws-6.8<6.8.0-1050.53~22.04.1

6.8.0-1050.53~22.04.1

ubuntu/linux-azure-5.19*

ubuntu/linux-azure-6.2*

ubuntu/linux-azure-6.5*

ubuntu/linux-azure-6.8<6.8.0-1051.57~22.04.1

6.8.0-1051.57~22.04.1

ubuntu/linux-azure-fde-5.19*

ubuntu/linux-azure-fde-6.2*

ubuntu/linux-azure-fde-6.8<6.8.0-1058.65~22.04.1

6.8.0-1058.65~22.04.1

ubuntu/linux-gcp-5.19*

ubuntu/linux-gcp-6.2*

ubuntu/linux-gcp-6.5*

ubuntu/linux-gcp-6.8<6.8.0-1052.55~22.04.1

6.8.0-1052.55~22.04.1

ubuntu/linux-hwe-5.19*

ubuntu/linux-hwe-6.2*

ubuntu/linux-hwe-6.5*

ubuntu/linux-hwe-6.8<6.8.0-106.106~22.04.1

6.8.0-106.106~22.04.1

ubuntu/linux-ibm-6.8<6.8.0-1049.49~22.04.1

6.8.0-1049.49~22.04.1

ubuntu/linux-intel-iot-realtime*

ubuntu/linux-lowlatency-hwe-5.19*

ubuntu/linux-lowlatency-hwe-6.2*

ubuntu/linux-lowlatency-hwe-6.5*

ubuntu/linux-lowlatency-hwe-6.8<6.8.0-106.106.1~22.04.1

6.8.0-106.106.1~22.04.1

ubuntu/linux-nvidia-6.2*

ubuntu/linux-nvidia-6.5*

ubuntu/linux-nvidia-6.8<6.8.0-1049.52~22.04.1

6.8.0-1049.52~22.04.1

ubuntu/linux-oem-5.17*

ubuntu/linux-oem-6.0*

ubuntu/linux-oem-6.1*

ubuntu/linux-oem-6.5*

ubuntu/linux-oracle-6.5*

ubuntu/linux-oracle-6.8<6.8.0-1047.48~22.04.1

6.8.0-1047.48~22.04.1

ubuntu/linux-realtime*

ubuntu/linux-riscv*

ubuntu/linux-riscv-5.19*

ubuntu/linux-riscv-6.5*

ubuntu/linux-riscv-6.8<6.8.0-106.106~22.04.1

6.8.0-106.106~22.04.1

ubuntu/linux-starfive-5.19*

ubuntu/linux-starfive-6.2*

ubuntu/linux-starfive-6.5*

ubuntu/linux-realtime-6.8<6.8.1-1045.46~22.04.1

6.8.1-1045.46~22.04.1

ubuntu/linux<6.8.0-106.106

6.8.0-106.106

ubuntu/linux-aws<6.8.0-1050.53

6.8.0-1050.53

ubuntu/linux-aws-6.14*

ubuntu/linux-aws-6.17<6.17.0-1009.9~24.04.2

6.17.0-1009.9~24.04.2

ubuntu/linux-azure<6.8.0-1051.57

6.8.0-1051.57

ubuntu/linux-azure-6.11*

ubuntu/linux-azure-6.14*

ubuntu/linux-azure-6.17<6.17.0-1010.10~24.04.1

6.17.0-1010.10~24.04.1

ubuntu/linux-azure-fde<6.8.0-1058.65

6.8.0-1058.65

ubuntu/linux-azure-fde-6.14*

ubuntu/linux-azure-nvidia<6.8.0-1039.42

6.8.0-1039.42

ubuntu/linux-azure-nvidia-6.14*

ubuntu/linux-gcp<6.8.0-1052.55

6.8.0-1052.55

ubuntu/linux-gcp-6.11*

ubuntu/linux-gcp-6.14*

ubuntu/linux-gcp-6.17<6.17.0-1009.9~24.04.3

6.17.0-1009.9~24.04.3

ubuntu/linux-gke<6.8.0-1048.53

6.8.0-1048.53

ubuntu/linux-gkeop<6.8.0-1035.38

6.8.0-1035.38

ubuntu/linux-hwe-6.11*

ubuntu/linux-hwe-6.14*

ubuntu/linux-hwe-6.17<6.17.0-19.19~24.04.2

6.17.0-19.19~24.04.2

ubuntu/linux-ibm<6.8.0-1049.49

6.8.0-1049.49

ubuntu/linux-lowlatency<6.8.0-106.106.1

6.8.0-106.106.1

ubuntu/linux-lowlatency-hwe-6.11*

ubuntu/linux-nvidia<6.8.0-1049.52

6.8.0-1049.52

ubuntu/linux-nvidia-6.11*

ubuntu/linux-nvidia-6.17<6.17.0-1018.18

6.17.0-1018.18

ubuntu/linux-nvidia-lowlatency<6.8.0-1049.52.1

6.8.0-1049.52.1

ubuntu/linux-nvidia-tegra<6.8.0-1020.20

6.8.0-1020.20

ubuntu/linux-oem-6.11*

ubuntu/linux-oem-6.14*

ubuntu/linux-oem-6.17<6.17.0-1017.17

6.17.0-1017.17

ubuntu/linux-oem-6.8*

ubuntu/linux-oracle<6.8.0-1047.48

6.8.0-1047.48

ubuntu/linux-oracle-6.14*

ubuntu/linux-oracle-6.17<6.17.0-1009.9~24.04.1

6.17.0-1009.9~24.04.1

ubuntu/linux-raspi<6.8.0-1050.54

6.8.0-1050.54

ubuntu/linux-raspi-realtime*

ubuntu/linux-realtime*

ubuntu/linux-riscv*

ubuntu/linux-riscv-6.14*

ubuntu/linux-riscv-6.17<6.17.0-19.19.1~24.04.1

6.17.0-19.19.1~24.04.1

ubuntu/linux-xilinx<6.8.0-1028.29

6.8.0-1028.29

ubuntu/linux-bluefield<6.8.0-1017.21

6.8.0-1017.21

ubuntu/linux-raspi-realtime<6.8.0-2040.41

6.8.0-2040.41

ubuntu/linux-realtime<6.8.1-1045.46

6.8.1-1045.46

ubuntu/linux-realtime-6.14*

ubuntu/linux-realtime-6.17<6.17.0-1008.9~24.04.1

6.17.0-1008.9~24.04.1

ubuntu/linux-aws-fips<6.8.0-1050.53+fips1

6.8.0-1050.53+fips1

ubuntu/linux-azure-fips<6.8.0-1052.58+fips1

6.8.0-1052.58+fips1

ubuntu/linux-fips<6.8.0-106.106+fips1

6.8.0-106.106+fips1

ubuntu/linux-gcp-fips<6.8.0-1052.55+fips1

6.8.0-1052.55+fips1

ubuntu/linux<6.17.0-19.19

6.17.0-19.19

ubuntu/linux-aws<6.17.0-1009.9

6.17.0-1009.9

ubuntu/linux-azure<6.17.0-1010.10

6.17.0-1010.10

ubuntu/linux-azure-fde*

ubuntu/linux-gcp<6.17.0-1009.9

6.17.0-1009.9

ubuntu/linux-oracle<6.17.0-1009.9

6.17.0-1009.9

ubuntu/linux-raspi<6.17.0-1010.10

6.17.0-1010.10

ubuntu/linux-realtime<6.17.0-1008.9

6.17.0-1008.9

ubuntu/linux-riscv<6.17.0-19.19.1

6.17.0-19.19.1

ubuntu/linux-vmware*

Remediation

Recommended actions to resolve this vulnerability, in priority order.

Upgrade
Upgrade ubuntu/linux-aws-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-1050.53~22.04.1
Upgrade
Upgrade ubuntu/linux-azure-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-1051.57~22.04.1
Upgrade
Upgrade ubuntu/linux-azure-fde-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-1058.65~22.04.1
Upgrade
Upgrade ubuntu/linux-gcp-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-1052.55~22.04.1
Upgrade
Upgrade ubuntu/linux-hwe-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-106.106~22.04.1
Upgrade
Upgrade ubuntu/linux-ibm-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-1049.49~22.04.1
Upgrade
Upgrade ubuntu/linux-lowlatency-hwe-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-106.106.1~22.04.1
Upgrade
Upgrade ubuntu/linux-nvidia-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-1049.52~22.04.1
Upgrade
Upgrade ubuntu/linux-oracle-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-1047.48~22.04.1
Upgrade
Upgrade ubuntu/linux-riscv-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.0-106.106~22.04.1
Upgrade
Upgrade ubuntu/linux-realtime-6.8 to a version that resolves this vulnerability.
Fixed in 6.8.1-1045.46~22.04.1
Upgrade
Upgrade ubuntu/linux to a version that resolves this vulnerability.
Fixed in 6.8.0-106.106
Upgrade
Upgrade ubuntu/linux-aws to a version that resolves this vulnerability.
Fixed in 6.8.0-1050.53
Upgrade
Upgrade ubuntu/linux-aws-6.17 to a version that resolves this vulnerability.
Fixed in 6.17.0-1009.9~24.04.2
Upgrade
Upgrade ubuntu/linux-azure to a version that resolves this vulnerability.
Fixed in 6.8.0-1051.57
Upgrade
Upgrade ubuntu/linux-azure-6.17 to a version that resolves this vulnerability.
Fixed in 6.17.0-1010.10~24.04.1
Upgrade
Upgrade ubuntu/linux-azure-fde to a version that resolves this vulnerability.
Fixed in 6.8.0-1058.65
Upgrade
Upgrade ubuntu/linux-azure-nvidia to a version that resolves this vulnerability.
Fixed in 6.8.0-1039.42
Upgrade
Upgrade ubuntu/linux-gcp to a version that resolves this vulnerability.
Fixed in 6.8.0-1052.55
Upgrade
Upgrade ubuntu/linux-gcp-6.17 to a version that resolves this vulnerability.
Fixed in 6.17.0-1009.9~24.04.3
Upgrade
Upgrade ubuntu/linux-gke to a version that resolves this vulnerability.
Fixed in 6.8.0-1048.53
Upgrade
Upgrade ubuntu/linux-gkeop to a version that resolves this vulnerability.
Fixed in 6.8.0-1035.38
Upgrade
Upgrade ubuntu/linux-hwe-6.17 to a version that resolves this vulnerability.
Fixed in 6.17.0-19.19~24.04.2
Upgrade
Upgrade ubuntu/linux-ibm to a version that resolves this vulnerability.
Fixed in 6.8.0-1049.49
Upgrade
Upgrade ubuntu/linux-lowlatency to a version that resolves this vulnerability.
Fixed in 6.8.0-106.106.1
Upgrade
Upgrade ubuntu/linux-nvidia to a version that resolves this vulnerability.
Fixed in 6.8.0-1049.52
Upgrade
Upgrade ubuntu/linux-nvidia-6.17 to a version that resolves this vulnerability.
Fixed in 6.17.0-1018.18
Upgrade
Upgrade ubuntu/linux-nvidia-lowlatency to a version that resolves this vulnerability.
Fixed in 6.8.0-1049.52.1
Upgrade
Upgrade ubuntu/linux-nvidia-tegra to a version that resolves this vulnerability.
Fixed in 6.8.0-1020.20
Upgrade
Upgrade ubuntu/linux-oem-6.17 to a version that resolves this vulnerability.
Fixed in 6.17.0-1017.17
Upgrade
Upgrade ubuntu/linux-oracle to a version that resolves this vulnerability.
Fixed in 6.8.0-1047.48
Upgrade
Upgrade ubuntu/linux-oracle-6.17 to a version that resolves this vulnerability.
Fixed in 6.17.0-1009.9~24.04.1
Upgrade
Upgrade ubuntu/linux-raspi to a version that resolves this vulnerability.
Fixed in 6.8.0-1050.54
Upgrade
Upgrade ubuntu/linux-riscv-6.17 to a version that resolves this vulnerability.
Fixed in 6.17.0-19.19.1~24.04.1
Upgrade
Upgrade ubuntu/linux-xilinx to a version that resolves this vulnerability.
Fixed in 6.8.0-1028.29
Upgrade
Upgrade ubuntu/linux-bluefield to a version that resolves this vulnerability.
Fixed in 6.8.0-1017.21
Upgrade
Upgrade ubuntu/linux-raspi-realtime to a version that resolves this vulnerability.
Fixed in 6.8.0-2040.41
Upgrade
Upgrade ubuntu/linux-realtime to a version that resolves this vulnerability.
Fixed in 6.8.1-1045.46
Upgrade
Upgrade ubuntu/linux-realtime-6.17 to a version that resolves this vulnerability.
Fixed in 6.17.0-1008.9~24.04.1
Upgrade
Upgrade ubuntu/linux-aws-fips to a version that resolves this vulnerability.
Fixed in 6.8.0-1050.53+fips1
Upgrade
Upgrade ubuntu/linux-azure-fips to a version that resolves this vulnerability.
Fixed in 6.8.0-1052.58+fips1
Upgrade
Upgrade ubuntu/linux-fips to a version that resolves this vulnerability.
Fixed in 6.8.0-106.106+fips1
Upgrade
Upgrade ubuntu/linux-gcp-fips to a version that resolves this vulnerability.
Fixed in 6.8.0-1052.55+fips1
Upgrade
Upgrade ubuntu/linux to a version that resolves this vulnerability.
Fixed in 6.17.0-19.19
Upgrade
Upgrade ubuntu/linux-aws to a version that resolves this vulnerability.
Fixed in 6.17.0-1009.9
Upgrade
Upgrade ubuntu/linux-azure to a version that resolves this vulnerability.
Fixed in 6.17.0-1010.10
Upgrade
Upgrade ubuntu/linux-gcp to a version that resolves this vulnerability.
Fixed in 6.17.0-1009.9
Upgrade
Upgrade ubuntu/linux-oracle to a version that resolves this vulnerability.
Fixed in 6.17.0-1009.9
Upgrade
Upgrade ubuntu/linux-raspi to a version that resolves this vulnerability.
Fixed in 6.17.0-1010.10
Upgrade
Upgrade ubuntu/linux-realtime to a version that resolves this vulnerability.
Fixed in 6.17.0-1008.9
Upgrade
Upgrade ubuntu/linux-riscv to a version that resolves this vulnerability.
Fixed in 6.17.0-19.19.1
Configuration
Allocate s32_pinctrl_desc with devm_kzalloc() instead of devm_kmalloc() so previously uninitialized fields, including num_custom_params, are initialized to zero.
Linux kernel pinctrl: s32cc s32_pinctrl_desc allocation in s32_pinctrl_probe() = devm_kzalloc()

Event History

Dec 16, 2025

CVE Published

via OSV·02:15 PM

Data Sourced

via OSV·02:15 PM

DescriptionSeverityAffected Software

Frequently Asked Questions

Which systems are most likely to experience this issue?

The reported failure occurs on systems using the NXP S32CC pin controller, with the example shown on an NXP S32G3 Reference Design Board. It can affect drivers that depend on pinctrl device-tree configuration, including the shown i.MX I2C driver probe path.

What are the observable symptoms?

Symptoms include intermittent allocation warnings during device probing, followed by pin configuration parsing failures. Dependent drivers may then fail to probe or operate correctly.

Is this an externally exploitable security issue?

The provided information describes an uninitialized-memory condition that causes allocation and device-tree pin configuration parse failures. It does not provide evidence of remote exploitation, privilege requirements, or code execution.

What change resolves the issue?

The resolution initializes all fields in s32_pinctrl_desc, including num_custom_params, rather than leaving fields uninitialized after allocation with devm_kmalloc().

UBUNTU-CVE-2025-68222: Low severity ubuntu/linux-hwe-edge vulnerability

Affected Software

Remediation

Event History

Frequently Asked Questions

Which systems are most likely to experience this issue?

What are the observable symptoms?

Is this an externally exploitable security issue?

What change resolves the issue?

Company

Resources

Contact

Frequently Asked Questions

Which systems are most likely to experience this issue?

What are the observable symptoms?

Is this an externally exploitable security issue?

What change resolves the issue?