vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Review the changes in version 4.0 of the Block Storage for VPC add-on.



 Change log for version 4.0.3_793, released 22 November 2021 

Review the changes in version 4.0.3_793 of the Block Storage for VPC add-on.



* Image tags: v4.0.3
* Image tags: v4.0.2
* Resolves the following CVEs.



* [CVE-2021-41772](https://nvd.nist.gov/vuln/detail/CVE-2021-41772)
* [CVE-2021-41771](https://nvd.nist.gov/vuln/detail/CVE-2021-41771)
* [CVE-2021-22946](https://nvd.nist.gov/vuln/detail/CVE-2021-22946)
* [CVE-2021-22947](https://nvd.nist.gov/vuln/detail/CVE-2021-22947)
* [CVE-2021-33928](https://nvd.nist.gov/vuln/detail/CVE-2021-33928)
* [CVE-2021-33929](https://nvd.nist.gov/vuln/detail/CVE-2021-33929)
* [CVE-2021-33930](https://nvd.nist.gov/vuln/detail/CVE-2021-33930)
* [CVE-2021-33938](https://nvd.nist.gov/vuln/detail/CVE-2021-33938)
* [CVE-2021-3733](https://nvd.nist.gov/vuln/detail/CVE-2021-3733)



* Updates the storage-secret-sidecar image to v1.1.3.
* Updates the default class policy from Reconcile to EnsureExists for the ibmc-vpc-block-10iops-tier storage class.
* Updates Golang to version 1.16.10.
Ubuntu 16.04 packages 4.4.0-201-generic 4.4.0-203-generic Updated worker node image with package updates for [CVE-2020-27619](https://nvd.nist.gov/vuln/detail/CVE-2020-27619), [CVE-2020-29372](https://nvd.nist.gov/vuln/detail/CVE-2020-29372), [CVE-2020-29374](https://nvd.nist.gov/vuln/detail/CVE-2020-29374), [CVE-2020-8625](https://nvd.nist.gov/vuln/detail/CVE-2020-8625), [CVE-2021-23840](https://nvd.nist.gov/vuln/detail/CVE-2021-23840), [CVE-2021-23841](https://nvd.nist.gov/vuln/detail/CVE-2021-23841), [CVE-2021-26937](https://nvd.nist.gov/vuln/detail/CVE-2021-26937), [CVE-2021-27212](https://nvd.nist.gov/vuln/detail/CVE-2021-27212), and [CVE-2021-3177](https://nvd.nist.gov/vuln/detail/CVE-2021-3177). 







 Change log for master fix pack 1.17.17_1555, released 22 February 2021 

The following table shows the changes that are in the master fix pack patch update 1.17.17_1555. Master patch updates are applied automatically.



Changes since version 1.17.17_1551

 Component Previous Current Description 

 Cluster health image v1.1.16 v1.1.18 Updated to use Go version 1.15.7. Updated image to implement additional IBM security controls. 
 Gateway-enabled cluster controller 1195 1232 Updated to use Go version 1.15.7.
RHEL 7 Packages 3.10.0-1160.11.1.el7 3.10.0-1160.15.2.el7 Updated worker node with image kernel and package updates for: [CVE-2020-10543](https://nvd.nist.gov/vuln/detail/CVE-2020-10543), [CVE-2020-10878](https://nvd.nist.gov/vuln/detail/CVE-2020-10878), [CVE-2020-12723](https://nvd.nist.gov/vuln/detail/CVE-2020-12723), [CVE-2020-15436](https://nvd.nist.gov/vuln/detail/CVE-2020-15436), [CVE-2020-35513](https://nvd.nist.gov/vuln/detail/CVE-2020-35513), [CVE-2019-25013](https://nvd.nist.gov/vuln/detail/CVE-2019-25013), [CVE-2020-10029](https://nvd.nist.gov/vuln/detail/CVE-2020-10029), [CVE-2020-29573](https://nvd.nist.gov/vuln/detail/CVE-2020-29573), and [CVE-2020-12321](https://nvd.nist.gov/vuln/detail/CVE-2020-12321)){: external}. 







 Change log for worker node fix pack 4.4.31_1532_openshift, released 1 February 2021 

The following table shows the changes that are in the worker node fix pack 4.4.31_1532_openshift. Worker node patch updates can be applied by updating, reloading (in classic infrastructure), or replacing (in VPC infrastructure) the worker node.



Changes since version 4.4.31_1530_openshift

 Component Previous Current Description
RHEL 7 Packages 3.10.0-1160.11.1.el7 3.10.0-1160.15.2.el7 Updated worker node with image kernel and package updates for: [CVE-2020-10543](https://nvd.nist.gov/vuln/detail/CVE-2020-10543), [CVE-2020-10878](https://nvd.nist.gov/vuln/detail/CVE-2020-10878), [CVE-2020-12723](https://nvd.nist.gov/vuln/detail/CVE-2020-12723), [CVE-2020-15436](https://nvd.nist.gov/vuln/detail/CVE-2020-15436), [CVE-2020-35513](https://nvd.nist.gov/vuln/detail/CVE-2020-35513), [CVE-2019-25013](https://nvd.nist.gov/vuln/detail/CVE-2019-25013), [CVE-2020-10029](https://nvd.nist.gov/vuln/detail/CVE-2020-10029), [CVE-2020-29573](https://nvd.nist.gov/vuln/detail/CVE-2020-29573), and [CVE-2020-12321](https://nvd.nist.gov/vuln/detail/CVE-2020-12321)){: external}. 







 Change log for worker node fix pack 4.5.28_1528_openshift, released 1 February 2021 

The following table shows the changes that are in the worker node fix pack 4.5.28_1528_openshift. Worker node patch updates can be applied by updating, reloading (in classic infrastructure), or replacing (in VPC infrastructure) the worker node.



Changes since version 4.5.24_1526_openshift

 Component Previous Current Description
IBM Cloud Controller Manager v1.11.10-286 v1.15.3-112 Updated to support the Kubernetes 1.15.3 release. 
 Red Hat OpenShift 3.11.141 3.11.146 See the [Red Hat OpenShift release notes](https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.htmlocp-3-11-146). Update resolves [CVE-2019-11247](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11247) (see the [IBM security bulletin](https://www.ibm.com/support/pages/node/1101957)) and [CVE-2019-11249](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11249) (see the [IBM security bulletin](https://www.ibm.com/support/pages/node/1102029)). 
 OpenVPN server 2.4.6-r3-IKS-115 2.4.6-r3-IKS-121 Image updated for [CVE-2019-1547](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1547) and [CVE-2019-1563](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1563). 
 RHEL 7 packages and kernel 3.10.0-1062.1.1 3.10.0-1062.1.2 Updated worker node images with kernel and package updates for [CVE-2019-1125](https://nvd.nist.gov/vuln/detail/CVE-2019-14835). 







 Change log for 3.11.141_1524_openshift, released 16 September 2019
Updated to use Go version 1.16.10. 
 Key Management Service provider v2.3.10 v2.3.12 Updated universal base image (UBI) to the latest 8.4 version to resolve CVEs. Updated to use Go version 1.16.10. 
 Load balancer and load balancer monitor for IBM Cloud Provider 1590 1659 Updated Alpine base image to the latest 3.14 version to resolve CVEs. Updated to use Go version 1.16.10. 
 Red Hat OpenShift 4.7.36 4.7.37 See the [Red Hat OpenShift release notes](https://docs.openshift.com/container-platform/4.7/release_notes/ocp-4-7-release-notes.htmlocp-4-7-37). 
 Red Hat OpenShift Control Plane Operator v4.7.0-20211109 v4.7.0-20211201 See the [Red Hat OpenShift on IBM Cloud toolkit release notes](https://github.com/openshift/ibm-roks-toolkit/releases/tag/v4.7.0+20211201). 
 OpenVPN Operator image v1.3.8 v1.3.9 Updated ansible operator base image to version v1.14.0 to resolve CVEs. 
 Red Hat OpenShift on IBM Cloud Metrics Server v4.7.0-20211109 v4.7.0-20211201 See the [Red Hat OpenShift on IBM Cloud toolkit release notes](https://github.com/openshift/ibm-roks-toolkit/releases/tag/v4.7.0+20211201). 
 Red Hat OpenShift on IBM Cloud toolkit 4.7.0+20211109 4.7.0+20211201 See the [Red Hat OpenShift on IBM Cloud toolkit release notes](https://github.com/openshift/ibm-roks-toolkit/releases/tag/v4.7.0+20211201). 







 Change log for worker node fix pack 4.7.38_1543_openshift, released 6 December 2021
For more information about setting the version by using the ibmcloud cr va-version-set command, see [ibmcloud cr va-version-set](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregcliic_cr_va_version_set) and [Setting the Vulnerability Advisor version](https://cloud.ibm.com/docs/Registry?topic=Registry-va_index&interface=uiva_set_version).

To find out which version of Vulnerability Advisor that you're running, see [ibmcloud cr va-version](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregcliic_cr_va_version).





 3 August 2022 

The CLI stops returning security status results in lists by default from version 1.0.0
: From IBM Cloud Container Registry CLI plug-in version 1.0.0, when you use the [ibmcloud cr image-list](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregclibx_cr_image_list) and [ibmcloud cr image-digests](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregclibx_cr_image_digests) commands to list images, they return Vulnerability Advisor security status results only if you use the --va option.

If you want to continue to receive security status with your lists, prepare to upgrade by adding the new --va option to your commands.

For more information, see [Container Registry CLI stops returning security status results in lists by default from version 1.0.0](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_notices_lists).





 8 July 2022 

Context-based restrictions
: You can use context-based restrictions to define and enforce access restrictions for IBM Cloud resources based on the network location of access requests.

For more information, see [Context-based restrictions](https://cloud.ibm.com/docs/Registry?topic=Registry-iam&interface=uiiam_cbr).





 5 July 2022
Managing Caveonix RiskForesight 



 Accessing the Caveonix RiskForesight console 

To manage the Caveonix RiskForesight™ service, you must access the Caveonix RiskForesight console by completing the following steps:



1. Use the IBM Cloud® infrastructure VPN or a jump server to allow access to the IP address of the Caveonix RiskForesight virtual machine (VM). You can find the IP address on the service details page for Caveonix RiskForesight in the IBM Cloud for VMware Solutions console. Complete the following steps:



1. Create a VPN password from the IBM Cloud infrastructure customer portal.
2. Log in to the data center VPN portal by using the IBM Cloud infrastructure VPN credentials.
3. Add the IP address and the hostname mapping into the hosts file from your local computer. Use the following format:

RiskForesight_VM_IP_Address RiskForesight_FQDN



2. To access the Caveonix RiskForesight console, click View RiskForesight console on the service details page for Caveonix RiskForesight. Then, log in by using the credentials that are listed on the same service details page.







 Applying updates to Caveonix RiskForesight 

You are responsible for maintaining Caveonix RiskForesight to keep it updated to the most recent version. You can download the required updates from the [Caveonix service provider portal](https://support.caveonix.com/login).

To obtain a login ID for the Caveonix service provider portal for product release notes and downloads, open a support case with the [IBM Cloud Support Center](https://cloud.ibm.com/unifiedsupport/supportcenter).

Provide the instance name that Caveonix is installed on, your company name, and an email address for your administrator for the support case. IBM Cloud Support acquires the credentials for your login and email your administrator.





 Updating Caveonix RiskForesight licenses 

This information does not apply to Caveonix Foresight that is installed on VMware® Regulated Workloads or Security and Compliance Readiness Bundle instances.
Select the controls that you want to add to your version.
4. Click Add.







 Run Code Risk Analyzer scan 

Scan your source code with Code Risk Analyzer to identify any security vulnerabilities that you need to assess.



1. Click Run scan.
2. Wait for the scan to finish.







 Add Security and Compliance Center scan 

Add the scans that you previously ran in Security and Compliance Center. Security and Compliance Center scans determine adherence to regulatory controls. For more information, see [Scheduling a scan](https://cloud.ibm.com/docs/security-compliance?topic=security-compliance-schedule-scan).



1. Select the profile that you scanned.
2. Select the Security and Compliance Center scan.
3. Click Add scan.
4. Click Next.









 Review requirements 

You must complete validation and any other requirements to publish your operator.





 Next steps 

Go to Partner Center and submit your request to publish your Operator to the IBM Cloud catalog.
HAProxy db4e6d 9b2dca Image update for [CVE-2020-1971](https://nvd.nist.gov/vuln/detail/CVE-2020-1971) and [CVE-2020-24659](https://nvd.nist.gov/vuln/detail/CVE-2020-24659). 
 Red Hat OpenShift 4.5.21 4.5.22 See the [Red Hat OpenShift release notes](https://docs.openshift.com/container-platform/4.5/release_notes/ocp-4-5-release-notes.htmlocp-4-5-22). 
 RHEL 7 Packages 3.10.0-1160.6.1.el7 3.10.0-1160.11.1.el7 Updated worker node image with kernel and package updates for: [CVE-2019-18282](https://nvd.nist.gov/vuln/detail/CVE-2019-18282), [CVE-2020-10769](https://nvd.nist.gov/vuln/detail/CVE-2020-10769), [CVE-2020-14314](https://nvd.nist.gov/vuln/detail/CVE-2020-14314), [CVE-2020-14385](https://nvd.nist.gov/vuln/detail/CVE-2020-14385), [CVE-2020-24394](https://nvd.nist.gov/vuln/detail/CVE-2020-24394), [CVE-2020-25212](https://nvd.nist.gov/vuln/detail/CVE-2020-25212), [CVE-2020-25643](https://nvd.nist.gov/vuln/detail/CVE-2020-25643), and [CVE-2020-1971](https://nvd.nist.gov/vuln/detail/CVE-2020-1971).
To add the Security and Compliance Center scan, run the [ibmcloud catalog offering version scc](https://cloud.ibm.com/docs/cli?topic=cli-manage-catalogs-pluginversion-scc) command:

ibmcloud catalog offering version scc --vl <VERSION_LOCATOR> --profile <PROFILE_ID> --scan <SCAN_ID>







 Reviewing requirements by using the console 

Make sure that you completed all of the required steps so that you can share the deployable architecture with others in your enterprise.





 Reviewing requirements by using the CLI 

You can make sure that you completed all of the required steps. To view the steps, see [Reviewing requirements by using the console](https://cloud.ibm.com/docs/secure-enterprise?topic=secure-enterprise-onboard-custom&interface=uicustom-tf-review-reqs-ui).
4.10.53 4.10.56 See the [change log](https://docs.openshift.com/container-platform/4.10/release_notes/ocp-4-10-release-notes.htmlocp-4-10-56). Updated to resolve [CVE-2022-3172](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-3172). For more information, see the [Security bulletin](https://www.ibm.com/support/pages/node/6997115). 
 OpenVPN Operator image v1.4.22 v1.4.23 Updated base image to resolve CVEs: [CVE-2022-4304](https://nvd.nist.gov/vuln/detail/CVE-2022-4304), [CVE-2022-4450](https://nvd.nist.gov/vuln/detail/CVE-2022-4450), [CVE-2023-0215](https://nvd.nist.gov/vuln/detail/CVE-2023-0215), [CVE-2023-0286](https://nvd.nist.gov/vuln/detail/CVE-2023-0286), [CVE-2023-0361](https://nvd.nist.gov/vuln/detail/CVE-2023-0361). 
 Portieris admission controller v0.13.3 v0.13.4 See the [Portieris admission controller release notes](https://github.com/IBM/portieris/releases/tag/v0.13.4).
Select a project.
5. Click Next.
6. Confirm or edit your workspace name.
7. Select a resource group.
8. Select a Schematics region.
9. Enter tags for your workspace. Tags provide a way to organize, track usage costs, and manage access to the resources in your account.
10. Click Next > Validate.







 Step 6: Manage compliance 

Controls are safeguards that are used to meet security and compliance requirements. Only controls that are supported by Security and Compliance Center, formatted correctly, and validated by Code Risk Analysis and Security and Compliance Center scans appear in the catalog. For more information, see [Formatting controls in your readme file](https://cloud.ibm.com/docs/sell?topic=sell-sell-format-controls).

You must validate your version before you can run a Code Risk Analyzer scan or add a Security and Compliance Center scan.



 Manage compliance controls 

You can review the controls that were added from your readme file and add additional controls.



1. Click Add controls.
2. Choose a profile.
3. Select the controls that you want to add to your version.
4. Click Add.







 Run Code Risk Analyzer scan 

Scan your source code with Code Risk Analyzer to identify any security vulnerabilities that you need to assess.



1. Click Run scan.
2. Wait for the scan to finish.







 Add Security and Compliance Center scan 

Add the scans that you previously ran in the Security and Compliance Center. Security and Compliance Center scans determine adherence to regulatory controls. For more information, see [Scheduling a scan](https://cloud.ibm.com/docs/security-compliance?topic=security-compliance-schedule-scan).



1. Select the profile that you scanned.
2. Select the Security and Compliance Center scan.
3. Click Add scan.
4. Click Next.









 Review requirements 

You must complete validation and any other requirements to publish your bundle.





 Next steps
* Addresses the following CVEs: [CVE-2021-3520](https://nvd.nist.gov/vuln/detail/CVE-2021-3520), [CVE-2021-3516](https://nvd.nist.gov/vuln/detail/CVE-2021-3516), [CVE-2021-3517](https://nvd.nist.gov/vuln/detail/CVE-2021-3517), [CVE-2021-3518](https://nvd.nist.gov/vuln/detail/CVE-2021-3518), [CVE-2021-3537](https://nvd.nist.gov/vuln/detail/CVE-2021-3537), [CVE-2021-3541](https://nvd.nist.gov/vuln/detail/CVE-2021-3541), [CVE-2021-33195](https://nvd.nist.gov/vuln/detail/CVE-2021-33195), [CVE-2021-33196](https://nvd.nist.gov/vuln/detail/CVE-2021-33196), [CVE-2021-33198](https://nvd.nist.gov/vuln/detail/CVE-2021-33198), [CVE-2021-33197](https://nvd.nist.gov/vuln/detail/CVE-2021-33197), and [CVE-2021-34558](https://nvd.nist.gov/vuln/detail/CVE-2021-34558).
* Includes a new version of the ibmc Helm plug-in.
* Adds support for Satellite clusters.
* Adds support for static provisioning of s3fs on AWS clusters.
* Adds support for installing the ibm-object-storage-plugin in air-gapped environments.
* Changes the default installation namespace from the kube-system namespace to the ibm-object-s3fs namespace.
RHEL 8 Packages 4.18.0-425.13.1 4.18.0-425.19.2 Worker node kernel & package updates for [CVE-2022-4269](https://nvd.nist.gov/vuln/detail/CVE-2022-4269), [CVE-2022-4304](https://nvd.nist.gov/vuln/detail/CVE-2022-4304), [CVE-2022-4378](https://nvd.nist.gov/vuln/detail/CVE-2022-4378), [CVE-2022-4450](https://nvd.nist.gov/vuln/detail/CVE-2022-4450), [CVE-2023-0215](https://nvd.nist.gov/vuln/detail/CVE-2023-0215), [CVE-2023-0266](https://nvd.nist.gov/vuln/detail/CVE-2023-0266), [CVE-2023-0286](https://nvd.nist.gov/vuln/detail/CVE-2023-0286), [CVE-2023-0361](https://nvd.nist.gov/vuln/detail/CVE-2023-0361), [CVE-2023-0386](https://nvd.nist.gov/vuln/detail/CVE-2023-0386). 
 Red Hat OpenShift on IBM Cloud. 4.11.32 4.11.34 For more information, see the [change log](https://docs.openshift.com/container-platform/4.11/release_notes/ocp-4-11-release-notes.htmlocp-4-11-34).
You can review the controls that were added from your readme file and add additional controls.



1. Click Add controls.
2. Choose a profile.
3. Select the controls that you want to add to your version.
4. Click Add.







 Run Code Risk Analyzer scan 

Scan your source code with Code Risk Analyzer to identify any security vulnerabilities that you need to assess.



1. Click Run scan.
2. Wait for the scan to finish.







 Add Security and Compliance Center scan 

Add the scans that you previously ran in the Security and Compliance Center. Security and Compliance Center scans determine adherence to regulatory controls. For more information, see [Scheduling a scan](https://cloud.ibm.com/docs/security-compliance?topic=security-compliance-schedule-scan).



1. Select the profile that you scanned.
2. Select the Security and Compliance Center scan.
3. Click Add scan.
4. Click Next.









 Review requirements 

You must complete validation and any other requirements to publish your product to your account.





 Next steps 

After you onboard and validate your virtual server image, you're ready to publish it to your account. From the Actions menu, select Publish to account. As a result, the virtual server image for Power Systems is available only to users who have access to the Sample virtual server image private catalog in your account.
RHEL 8 Packages 4.18.0-425.13.1 4.18.0-425.19.2 Worker node kernel & package updates for [CVE-2022-4269](https://nvd.nist.gov/vuln/detail/CVE-2022-4269), [CVE-2022-4304](https://nvd.nist.gov/vuln/detail/CVE-2022-4304), [CVE-2022-4378](https://nvd.nist.gov/vuln/detail/CVE-2022-4378), [CVE-2022-4450](https://nvd.nist.gov/vuln/detail/CVE-2022-4450), [CVE-2023-0215](https://nvd.nist.gov/vuln/detail/CVE-2023-0215), [CVE-2023-0266](https://nvd.nist.gov/vuln/detail/CVE-2023-0266), [CVE-2023-0286](https://nvd.nist.gov/vuln/detail/CVE-2023-0286), [CVE-2023-0361](https://nvd.nist.gov/vuln/detail/CVE-2023-0361), [CVE-2023-0386](https://nvd.nist.gov/vuln/detail/CVE-2023-0386). 
 Red Hat OpenShift on IBM Cloud. 4.12.8 4.12.10 For more information, see the [change log](https://docs.openshift.com/container-platform/4.12/release_notes/ocp-4-12-release-notes.htmlocp-4-12-10).
RHEL 8 Packages 4.18.0-425.13.1 4.18.0-425.19.2 Worker node kernel & package updates for [CVE-2022-4269](https://nvd.nist.gov/vuln/detail/CVE-2022-4269), [CVE-2022-4304](https://nvd.nist.gov/vuln/detail/CVE-2022-4304), [CVE-2022-4378](https://nvd.nist.gov/vuln/detail/CVE-2022-4378), [CVE-2022-4450](https://nvd.nist.gov/vuln/detail/CVE-2022-4450), [CVE-2023-0215](https://nvd.nist.gov/vuln/detail/CVE-2023-0215), [CVE-2023-0266](https://nvd.nist.gov/vuln/detail/CVE-2023-0266), [CVE-2023-0286](https://nvd.nist.gov/vuln/detail/CVE-2023-0286), [CVE-2023-0361](https://nvd.nist.gov/vuln/detail/CVE-2023-0361), [CVE-2023-0386](https://nvd.nist.gov/vuln/detail/CVE-2023-0386). 
 Red Hat OpenShift on IBM Cloud. 4.10.54 4.10.55 For more information, see the [change log](https://docs.openshift.com/container-platform/4.10/release_notes/ocp-4-10-release-notes.htmlocp-4-10-55).
RHEL 8 Packages 4.18.0-425.13.1 4.18.0-425.19.2 Worker node kernel & package updates for [CVE-2022-4269](https://nvd.nist.gov/vuln/detail/CVE-2022-4269), [CVE-2022-4304](https://nvd.nist.gov/vuln/detail/CVE-2022-4304), [CVE-2022-4378](https://nvd.nist.gov/vuln/detail/CVE-2022-4378), [CVE-2022-4450](https://nvd.nist.gov/vuln/detail/CVE-2022-4450), [CVE-2023-0215](https://nvd.nist.gov/vuln/detail/CVE-2023-0215), [CVE-2023-0266](https://nvd.nist.gov/vuln/detail/CVE-2023-0266), [CVE-2023-0286](https://nvd.nist.gov/vuln/detail/CVE-2023-0286), [CVE-2023-0361](https://nvd.nist.gov/vuln/detail/CVE-2023-0361), [CVE-2023-0386](https://nvd.nist.gov/vuln/detail/CVE-2023-0386). 
 Red Hat OpenShift on IBM Cloud. 4.9.57 4.9.59 For more information, see the [change log](https://docs.openshift.com/container-platform/4.9/release_notes/ocp-4-9-release-notes.htmlocp-4-9-59).
Red Hat OpenShift 4.6.31 4.6.34 See the [Red Hat OpenShift release notes](https://docs.openshift.com/container-platform/4.6/release_notes/ocp-4-6-release-notes.htmlocp-4-6-34). 
 RHEL 7 Packages 3.10.0-1160.25 3.10.0-1160.31 Updated worker node image with kernel package updates for [CVE-2020-8648](https://nvd.nist.gov/vuln/detail/CVE-2020-8648), [CVE-2020-12362](https://nvd.nist.gov/vuln/detail/CVE-2020-12362)[CVE-2020-12363](https://nvd.nist.gov/vuln/detail/CVE-2020-12363)[CVE-2020-12364](https://nvd.nist.gov/vuln/detail/CVE-2020-12364)[CVE-2020-27170](https://nvd.nist.gov/vuln/detail/CVE-2020-27170)[CVE-2021-3347](https://nvd.nist.gov/vuln/detail/CVE-2021-3347), [CVE-2020-24489](https://nvd.nist.gov/vuln/detail/CVE-2020-24489), [CVE-2020-24511](https://nvd.nist.gov/vuln/detail/CVE-2020-24511)[CVE-2020-24512](https://nvd.nist.gov/vuln/detail/CVE-2020-24512), [CVE-2020-24513](https://nvd.nist.gov/vuln/detail/CVE-2020-24513) and [CVE-2021-25217](https://nvd.nist.gov/vuln/detail/CVE-2021-25217).
RHEL 8 Packages 4.18.0-425.10.1 4.18.0-425.13.1 Worker node & kernel package updates for [CVE-2020-10735](https://nvd.nist.gov/vuln/detail/CVE-2020-10735), [CVE-2021-28861](https://nvd.nist.gov/vuln/detail/CVE-2021-28861), [CVE-2022-2873](https://nvd.nist.gov/vuln/detail/CVE-2022-2873), [CVE-2022-40897](https://nvd.nist.gov/vuln/detail/CVE-2022-40897), [CVE-2022-41222](https://nvd.nist.gov/vuln/detail/CVE-2022-41222), [CVE-2022-43945](https://nvd.nist.gov/vuln/detail/CVE-2022-43945), [CVE-2022-4415](https://nvd.nist.gov/vuln/detail/CVE-2022-4415), [CVE-2022-45061](https://nvd.nist.gov/vuln/detail/CVE-2022-45061), [CVE-2022-48303](https://nvd.nist.gov/vuln/detail/CVE-2022-48303). 
 Red Hat OpenShift on IBM Cloud. 4.9.54 4.9.56 For more information, see the [change log](https://docs.openshift.com/container-platform/4.9/release_notes/ocp-4-9-release-notes.htmlocp-4-9-56).