Skip to content

Address kernel CVE-2024-36288, CVE-2024-38662, CVE-2024-38780, CVE-2024-39277, CVE-2024-39292#9612

Merged
christopherco merged 1 commit intomainfrom
rlmenge/2.0/kernel-cves-future
Jul 26, 2024
Merged

Address kernel CVE-2024-36288, CVE-2024-38662, CVE-2024-38780, CVE-2024-39277, CVE-2024-39292#9612
christopherco merged 1 commit intomainfrom
rlmenge/2.0/kernel-cves-future

Conversation

@rlmenge
Copy link
Copy Markdown
Contributor

@rlmenge rlmenge commented Jul 5, 2024

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

  • The toolchain has been rebuilt successfully (or no changes were made to it)
  • The toolchain/worker package manifests are up-to-date
  • Any updated packages successfully build (or no packages were changed)
  • Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
  • Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
  • All package sources are available
  • cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
  • LICENSE-MAP files are up-to-date (./SPECS/LICENSES-AND-NOTICES/data/licenses.json, ./SPECS/LICENSES-AND-NOTICES/LICENSES-MAP.md, ./SPECS/LICENSES-AND-NOTICES/LICENSE-EXCEPTIONS.PHOTON)
  • All source files have up-to-date hashes in the *.signatures.json files
  • sudo make go-tidy-all and sudo make go-test-coverage pass
  • Documentation has been updated to match any changes to the build system
  • If you are adding/removing a .spec file that has multiple-versions supported, please add @microsoft/cbl-mariner-multi-package-reviewers team as reviewer (Eg. golang has 2 versions 1.18, 1.21+)
  • Ready to merge

Summary

Address kernel CVE-2024-36288, CVE-2024-38662, CVE-2024-38780, CVE-2024-39277, CVE-2024-39292

Change Log
Does this affect the toolchain?

NO

Links to CVEs

@rlmenge rlmenge changed the title [REQUIRES kernel 5.15.161.] Address kernel CVE-2024-36288, CVE-2024-38662, CVE-2024-38780, CVE-2024-39277, CVE-2024-39292 [REQUIRES kernel 5.15.161] Address kernel CVE-2024-36288, CVE-2024-38662, CVE-2024-38780, CVE-2024-39277, CVE-2024-39292 Jul 5, 2024
@microsoft-github-policy-service microsoft-github-policy-service Bot added security main PR Destined for main labels Jul 5, 2024
@rlmenge rlmenge changed the title [REQUIRES kernel 5.15.161] Address kernel CVE-2024-36288, CVE-2024-38662, CVE-2024-38780, CVE-2024-39277, CVE-2024-39292 Address kernel CVE-2024-36288, CVE-2024-38662, CVE-2024-38780, CVE-2024-39277, CVE-2024-39292 Jul 16, 2024
@rlmenge rlmenge marked this pull request as ready for review July 16, 2024 18:29
@rlmenge rlmenge requested a review from a team as a code owner July 16, 2024 18:29
@christopherco christopherco merged commit b9c5a1a into main Jul 26, 2024
@christopherco christopherco deleted the rlmenge/2.0/kernel-cves-future branch July 26, 2024 23:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

main PR Destined for main security

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants