How many CVEs have patched do_allocate_publickey?

1 published CVEs changed do_allocate_publickey in OP-TEE/optee_os, in 3 distinct patches totalling 12 changed lines, between 2023 and 2023.

What is the latest CVE that changed do_allocate_publickey?

CVE-2023-41325, published 2023-09-15, changed lines 361 to 363 of core/drivers/crypto/caam/acipher/caam_dsa.c.

How does do_allocate_publickey compare to the rest of OP-TEE/optee_os?

OP-TEE/optee_os has 17 CVEs with a located fix in total; 1 of them changed do_allocate_publickey.

What do the line numbers refer to?

Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

RadicalNotion.AI

Log in Create an account

OP-TEE/optee_os

Function

3 files

do_allocate_publickey

Name: do_allocate_publickey in OP-TEE/optee_os: CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

Defined in 3 files

Last patched September 15, 2023

1

CVEs

That changed this function

3

Distinct patches

Backports counted once

12

Lines changed

Added plus removed

2023

Years

By CVE publication date

Overview

do_allocate_publickey in OP-TEE/optee_os was changed by 1 published CVE fixes in 2023, in 3 distinct patches that added or removed 12 lines in total.

The name occurs in 3 files: core/drivers/crypto/caam/acipher/caam_rsa.c, core/drivers/crypto/caam/acipher/caam_dsa.c, core/drivers/crypto/caam/acipher/caam_ecc.c.

OP-TEE/optee_os has 17 CVEs with a located fix in total, so 6% of them touched this function.

CVEs that patched it

Every published CVE whose fix changed do_allocate_publickey, newest first, with the lines each fix touched.

CVE-2023-41325
CVE-2023-41325 · core/drivers/crypto/caam/acipher/caam_dsa.c · lines 361–363 · +3 −3
High · CVSS 7.4
EPSS 0.4%2023-09-15
CVE-2023-41325
CVE-2023-41325 · core/drivers/crypto/caam/acipher/caam_ecc.c · line 210 · +1 −1
High · CVSS 7.4
EPSS 0.4%2023-09-15
CVE-2023-41325
CVE-2023-41325 · core/drivers/crypto/caam/acipher/caam_rsa.c · lines 438–439 · +2 −2
High · CVSS 7.4
EPSS 0.4%2023-09-15

Get an alert when the next CVE fix lands in OP-TEE/optee_os, with the patched functions.

Monitor optee_os CVEs

Other functions in these files

Functions in the same files that CVE fixes also changed.

Other hotspots in the repository

Functions in OP-TEE/optee_os changed by the most CVE fixes.

syscall_cryp_derive_key2 CVEs · core/tee/tee_svc_cryp.c uses2 CVEs · lib/libmpa/mpa_expmod.c exptmod2 CVEs · core/lib/libtomcrypt/src/mpa_desc.c rsa_exptmod2 CVEs · core/lib/libtomcrypt/src/pk/rsa/rsa_exptmod.c rand2 CVEs · core/lib/libtomcrypt/src/mpa_desc.c calculates2 CVEs · core/lib/libtomcrypt/src/mpa_desc.c

All patched functions in OP-TEE/optee_os

Frequently asked questions

Common questions about CVE fixes to do_allocate_publickey.

How many CVEs have patched do_allocate_publickey?: 1 published CVEs changed do_allocate_publickey in OP-TEE/optee_os, in 3 distinct patches totalling 12 changed lines, between 2023 and 2023.
What is the latest CVE that changed do_allocate_publickey?: CVE-2023-41325, published 2023-09-15, changed lines 361 to 363 of core/drivers/crypto/caam/acipher/caam_dsa.c.
How does do_allocate_publickey compare to the rest of OP-TEE/optee_os?: OP-TEE/optee_os has 17 CVEs with a located fix in total; 1 of them changed do_allocate_publickey.
What do the line numbers refer to?: Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

References

Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.

Track OP-TEE/optee_os CVEs

Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.

Create an account See pricing