Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @


From EGIWiki
Jump to navigation Jump to search
Main page Software Security Checklist Issue Handling Advisories Notes On Risk Advisory Template More


Title:       EGI SVG 'ADVISORY' [TLP:WHITE] HIGH risk. Microarchitectural Store Buffer Data vulnerability 
              affecting Intel Processors - CVE-2018-12130, CVE-2018-12126, CVE-2018-12127, and CVE-2019-1109 

Date:        2019-05-16

Affected software and risk

HIGH risk vulnerabilities concerning Microarchitectural Data Sampling (MDS) affecting Intel microprocessors  

Package : Linux kernel/Chip design
CVE ID  :  CVE-2018-12126, CVE-2018-12127, CVE-2018-12130, and CVE-2019-11091 

Intel released a statement regarding Microarchitectural Data Sampling (MDS), a new set of hardware-level 
security vulnerabilities affecting microprocessors related to the way that microprocessor chips cache memory 
have been disclosed. This allows privilege escalation and unauthorized access to user data. [R 1] [R 2]

Updated versions of the /intel-microcode/, /qemu, xen/ and /linux/ kernel packages are being published. 

Actions required/recommended

Sites should apply vendor kernel updates as soon as possible. 

Component installation information

For RedHat see [R 5]

For Scientific Linux see [R 6]  (patch not available yet)

For CentoS see [R 7]

For Ubuntu see [R 8]

For Debian see [R 9]

The CERN Computer Security team have provided further information, some of which could be useful also to 
other sites.  See [R 13]

More information, especially concerning hypervisors, may be added later.

More information

See [R 10], [R 11] for detailed explanations of these vulnerabilities. 

As far as the EGI SVG is aware, this only affects Intel Processors. 


** WHITE information - Unlimited distribution 
   - see for distribution restrictions **                       

Minor updates may be made without re-distribution to the sites


Comments or questions should be sent to svg-rat  at

If you find or become aware of another vulnerability which is relevant to EGI you may report it by e-mail to  

report-vulnerability at
the EGI Software Vulnerability Group will take a look according to the procedure defined in [R 12]  

Note that this is undergoing revision to fully handle vulnerabilities in the EOSC-hub era. 


[R 1]

[R 2]

[R 3]

[R 4]

[R 5]

[R 6]

[R 7]

[R 8]  

[R 9]  

[R 10]

[R 11]

[R 12]

[R 13]


SVG was alerted to this vulnerability by Vincent Brillault 

Yyyy-mm-dd  [EGI-SVG-2019-CVE-2018-12126] 

2019-05-14 SVG alerted to this issue by Vincent Brillault from SVG/EGI CSIRT
2019-05-15 Investigation of vulnerability and relevance to EGI carried out 
2019-05-15 Advisory drafted
2019-05-15 EGI SVG Risk Assessment completed
2019-05-15 Updated packages available 
2019-05-16 Advisory sent to sites


This advisory has been prepared as part of the effort to fulfil EGI SVG's purpose 
"To minimize the risk to the EGI infrastructure arising from software vulnerabilities"

The risk is that assessed by the group, according to the EGI SVG issue handling procedure [R 10]  in the context of how the software is used in the EGI infrastructure. It is the opinion of the group, we do not guarantee it to be correct. The risk may also be higher or lower in other deployments depending on how the software is used.   

Others may re-use this information provided they:-

1) Respect the provided TLP classification

2) Credit the EGI Software Vulnerability Group

Note that the SVG issue handling procedure is currently under review, to take account of the increasing inhomogeneity of the EGI infrastructure and the services in the EOSC-hub catalogue.

On behalf of the EGI SVG,